Junit Framework
Approved changes feed: RSS · Atom
cpe:2.3:a:junit-team:junit-framework:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Junit Team (d4f501e2-238a-5444-813b-228d43b5361b) |
|---|---|
| Product | Junit Framework (3e0148d5-8896-5bc1-a965-d2a15cedc310) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2025-53103 |
vulnerable | 2026-06-08 07:31:13.957251 |
JUnit OpenTestReportGeneratingListener can leak Git credentials
MEDIUM (5.8)
JUnit is a testing framework for Java and the JVM. From version 5.12.0 to 5.13.1, JUnit's support for writing Open Test Reporting XML files can leak Git credentials. The impact depends on the level of the access token exposed through the OpenTestReportGeneratingListener. 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. This issue as been patched in version 5.13.2.
Published: 2025-07-01T18:02:39.060Z
Updated: 2025-07-01T18:50:18.904Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.