Git credential disclosure via unredacted report URLs
Published Jul 1, 2025 · Updated Jul 1, 2025
Cleartext credential exposure in JUnit Framework 5.12.0 through 5.13.1 allows attackers to read Git credentials from shared XML reports. OpenTestReportGeneratingListener copies user information from Git remote.origin.url into the originUrl attribute without redacting embedded credentials. Exposure requires opt-in Open Test Reporting, a credential-bearing remote URL, and access to a report; stolen tokens permit actions within their granted scope.
Summary
What happened
Cleartext credential exposure in JUnit Framework 5.12.0 through 5.13.1 allows attackers to read Git credentials from shared XML reports. OpenTestReportGeneratingListener copies user information from Git remote.origin.url into the originUrl attribute without redacting embedded credentials. Exposure requires opt-in Open Test Reporting, a credential-bearing remote URL, and access to a report; stolen tokens permit actions within their granted scope.
The record
- CVE
- CVE-2025-53103
- Published
- Jul 1, 2025
- Updated
- Jul 1, 2025
- Vendor
- JUnit
- Product
- JUnit Framework
- Classifications
- CWE-312, CAPEC-37, T1552.001
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jul 1, 2025CVE publishedPublication date reported by the CVE source.
- Jul 1, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 5.12.0, < 5.13.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- OpenTestReportGeneratingListener credential-leak proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo