CVE-2025-24355: Updatecli exposes Maven credentials in console output
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.
Published Jan 24, 2025
Affected packages
github.com/updatecli/updatecli
- Ecosystem
- Go
- Affected
- < 0.93.0
- Fixed in
- 0.93.0
- Check
go list -m github.com/updatecli/updatecli
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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 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.xmlbut 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 errorImpact
User credentials/token used to authenticate against a private maven repository can be leaked in clear-text in console or CI logs.
Credited to gionn, olblak.
References
- https://github.com/updatecli/updatecli/security/advisories/GHSA-v34r-vj4r-38j6
- https://nvd.nist.gov/vuln/detail/CVE-2025-24355
- https://github.com/updatecli/updatecli/commit/344b28091ffeca5ed32e8d0f9eda542842fcd3fa
- https://www.updatecli.io/docs/plugins/resource/maven
- https://github.com/advisories/GHSA-v34r-vj4r-38j6
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
