Medium, CVSS 5.8MavenPublished
junit-platform-reporting can leak Git credentials through its OpenTestReportGeneratingListener
CVE-2025-53103 · GHSA-m43g-m425-p68x
- Affected
- Maven org.junit.platform:junit-platform-reporting >= 5.12.0, <= 5.13.1
- Fixed in
- 5.13.2· Vendor fix available
- Issue
- This vulnerability affects JUnit's support for writing Open Test Reporting XML files which is an opt-in feature of junit-platform-reporting. If a repository is cloned using a GitHub token or other credentials in its URL, for example: The credentials are captured by OpenTestReportGeneratingListener which produces (trimmed for brevity): Details https://github.com/junit-team/junit5/blob/6b7764dac92fd35cb348152d1b37f8726875a4e0/junit-platform-reporting/src/main/java/org/junit/platform/reporting/open/xml/OpenTestReportGeneratingListener.java#L183 I think this should be configurable in some way to exclude select git information or exclude it entirely. PoC 1. Clone a repo using a GitHub token as shown above. 2. Enable the listener junit.platform.reporting.open.xml.enabled=true 3. Observe report captures credentials Impact Depending on the level of access of the token, it can be nothing, limited, or everything. If these test reports are published or stored anywhere public, then there…
Recommended action: Upgrade to 5.13.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.