FlawAtlas
Search the atlas
CVE-2025-24355 High

Updatecli exposes Maven credentials in console output in github.com/updatecli/updatecli

Updatecli exposes Maven credentials in console output in github.com/updatecli/updatecli

Exploit probability 0.2%
Published January 28, 2025
Required by Not available
Last source change March 3, 2026

02 / AFFECTED SOFTWARE

Affected packages

Unknown Unknown

201 explicit affected versions

Go github.com/updatecli/updatecli
Go github.com/updatecli/updatecli

03 / CONNECTIONS

Connected vulnerabilities

04 / EVIDENCE

Source records

Open Source Vulnerabilities CVE-2025-24355

Updatecli is a tool used to apply file update strategies. Prior to version 0.93.0, private maven repository credentials may be leaked in application logs in case of unsuccessful retrieval operation. During the execution of an updatecli pipeline which contains a `maven` source configured with basic auth credentials, the credentials are being leaked in the application execution logs in case of failure. Credentials are properly sanitized when the operation is successful but not when for whatever reason there is a failure in the maven repository, e.g. wrong coordinates provided, not existing artifact or version. Version 0.93.0 contains a patch for the issue.

View original source
Open Source Vulnerabilities GO-2025-3419

Updatecli exposes Maven credentials in console output in github.com/updatecli/updatecli

View original source
Open Source Vulnerabilities GHSA-v34r-vj4r-38j6

### Summary Private maven repository credentials leaked in application logs in case of unsuccessful retrieval operation. ### Details During the execution of an updatecli pipeline which contains a `maven` source configured with basic auth credentials, the credentials are being leaked in the application execution logs in case of failure. Credentials are properly sanitized when the operation is successful but not when for whatever reason there is a failure in the maven repository .e.g. wrong coordinates provided, not existing artifact or version. ### PoC The [documentation](https://www.updatecli.io/docs/plugins/resource/maven/) currently state to provide user credentials as basic auth inside the `repository` field. e.g. ``` sources: default: kind: maven spec: repository: "{{ requiredEnv "MAVEN_USERNAME" }}:{{ requiredEnv "MAVEN_PASS" }}@repo.example.org/releases" groupid: "org.example.company" artifactid: "my-artifact" versionFilter: kind: regex pattern: "^23(\.[0-9]+){1,2}$" ``` Logs are sanitized properly in case of a successful operation: ``` source: source#default ----------------------------------------------------------- Searching for version matching pattern "^23(\\.[0-9]+){1,2}$" ✔ Latest version is 23.4.0 on the Maven repository at https://repo.example.org/releases/org/example/company/my-artifact/maven-metadata.xml ``` but leaks credentials in case the GAV coordinates are wrong (misspelled package name or missing): ``` source: source#default ----------------------------------------------------------- ERROR: ✗ getting latest version: URL "https://REDACTED:[email protected]/releases/org/example/company/wrong-artifact/maven-metadata.xml" not found or in error ``` ### Impact User credentials/token used to authenticate against a private maven repository can be leaked in clear-text in console or CI logs.

View original source

05 / REFERENCES

Further evidence