{"answers":{"affected":"2 open source packages ship an affected version, including org.junit.platform:junit-platform-reporting.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-53103 exists.","fix":"Upgrade org.junit.platform:junit-platform-reporting to 5.13.2 or later.","what":"CVE-2025-53103 is a medium-severity vulnerability in junit-team junit-framework, published on 1 Jul 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-53103 and fix it if it is affected.\n\nWhat it is: CVE-2025-53103 is a medium-severity vulnerability in junit-team junit-framework, published on 1 Jul 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-53103 exists.\n\nAffected packages and fixed versions:\n- org.junit.platform:junit-platform-reporting (Maven): affected from 5.12.0; fixed in 5.13.2\n- org.junit.platform:junit-platform-reporting (Maven): affected from 5.12.0; fixed in 5.13.2\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-53103/ (Markdown: https://insights.sbomify.com/CVE-2025-53103/index.md)","id":"CVE-2025-53103","markdown":"https://insights.sbomify.com/CVE-2025-53103/index.md","name":"CVE-2025-53103","record":{"aliases":["GHSA-m43g-m425-p68x","UBUNTU-CVE-2025-53103"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","account_takeover"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Java testing framework","requires_auth":"high_privilege","summary":"JUnit's Open Test Reporting listener may leak Git credentials in generated XML files, allowing attackers to steal tokens and impersonate users if reports are public.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-312","name":"Cleartext Storage of Sensitive Information"}],"description":"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.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"JUnit OpenTestReportGeneratingListener can leak Git credentials","id":"CVE-2025-53103","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":2,"n_references":2,"next":{"headline":"gluestack-ui Command Injection Vulnerability via discussion-to-slack GitHub Action Workflow","id":"CVE-2025-53104"},"packages":[{"ecosystem":"Maven","fixed":["5.13.2"],"introduced":["5.12.0"],"last_affected":[],"package":"org.junit.platform:junit-platform-reporting","purl":null,"source":"GHSA-m43g-m425-p68x"},{"ecosystem":"Maven","fixed":["5.13.2"],"introduced":["5.12.0"],"last_affected":[],"package":"org.junit.platform:junit-platform-reporting","purl":"pkg:maven/org.junit.platform/junit-platform-reporting","source":"GHSA-m43g-m425-p68x"}],"prev":{"headline":"Discourse's WebAuthn challenge isn't cleared from user session after authentication","id":"CVE-2025-53102"},"products":["junit-framework"],"published":"2025-07-01","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-07-01","vendors":["junit-team"]},"summary":"JUnit's Open Test Reporting listener may leak Git credentials in generated XML files, allowing attackers to steal tokens and impersonate users if reports are public.","url":"https://insights.sbomify.com/CVE-2025-53103/"}