junit-platform-reporting can leak Git credentials through its OpenTestReportGeneratingListener
Date: 2025-07
Affected: maven/org.junit.platform:junit-platform-reporting
Attack vector: deepfake
Category: vulnerability-disclosure
Severity: Medium
CVE: CVE-2025-53103
CWE: CWE-312
CVSS: 5.8 (CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:N)

### Summary 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: ```bash git clone https://${GH_APP}:${GH_TOKEN}@github.com/example/example.git ``` The credentials are captured by `OpenTestReportGeneratingListener` which produces (trimmed for brevity): ```xml <infrastructure> <git:repository originUrl="https://username:token@github.com/example/example.git" /> </infrastructure> ``` ### 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 is the possibility that a rouge attacker can steal the token and perform elevated actions by impersonating the user or app. ### Resolution JUnit 5.13.2 and later replace credentials in the URL with `***`. Moreover, including any Git metadata in t


Mitigations:

Architectural layers (MAESTRO):