WaratekVRT Sign in
Reset
More filters (1)
Columns
Including CVEs outside Waratek scope✕Product junit✕
Overview 8 matches · 3 protected · 0 exploited · 0 CISA KEV · 0 public PoC · 1 EPSS ≥ 0.5
8matches 3protected37.5% 0exploited0.0% 0CISA KEV0.0% 0public PoC0.0% 1EPSS ≥ 0.512.5%
Protected by Waratek 3 37.5% Rule in development 0 0.0% Mitigation candidate 0 0.0% No exploit published 5 62.5% Outside Waratek scope 0 0.0% Not applicable 0 0.0% Withdrawn CVE 0 0.0%
Critical 0 0.0% High 2 25.0% Medium 6 75.0% Low 0 0.0% None 0 0.0% Unknown 0 0.0%
blocked by ARMR today 3 37.5% partly blocked 0 0.0% not blocked 5 62.5% not established 0 0.0% unrecorded 0 0.0%
Exploited 0 0.0% Working exploit published 0 0.0% Proof of concept only 2 25.0% Forecast only 1 12.5% No public exploit 5 62.5%
split by peak 2 / year
No exploit published: 5Protected by Waratek: 3 Medium: 6High: 2 not blocked: 5blocked by ARMR today: 3 No public exploit: 5Forecast only: 1Proof of concept only: 2
20181 Protected by Waratek1 High1 blocked by ARMR today1 No public exploit1 20191 No exploit published1 Medium1 not blocked1 No public exploit1 20201 Protected by Waratek1 Medium1 blocked by ARMR today1 No public exploit1 20210 20222 No exploit published2 Medium2 not blocked2 Forecast only1 No public exploit1 20231 No exploit published1 Medium1 not blocked1 No public exploit1 20240 20252 Protected by Waratek1 No exploit published1 High1 Medium1 blocked by ARMR today1 not blocked1 Proof of concept only2
20182019202020212022202320242025
8 matches Sign in to download these CVEs as CSV or JSON, or to follow them in a feed.
CVE Severity Published▾ Status Exploitation Description
CVE-2025-53103 Medium 2025-07-01 No exploit published Proof of concept only 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.
CVE-2025-52888 High 2025-06-24 Protected by Waratek Proof of concept only Allure 2 is the version 2.x branch of Allure Report, a multi-language test reporting tool. A critical XML External Entity (XXE) vulnerability exists in the xunit-xml-plugin used by Allure 2 prior to version 2.34.1. The plugin fails to securely configure the XML parser (`DocumentBuilderFactory`) and allows external entity expansion when processing test result .xml files. This allows attackers to read arbitrary files from the file system and potentially trigger server-side request forgery (SSRF). Version 2.34.1 contains a patch for the issue.
CVE-2023-25761 Medium 2023-02-15 No exploit published No public exploit Jenkins JUnit Plugin 1166.va_436e268e972 and earlier does not escape test case class names in JavaScript expressions, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to control test case class names in the JUnit resources processed by the plugin.
CVE-2022-45380 Medium 2022-11-15 No exploit published No public exploit Jenkins JUnit Plugin 1159.v0b_396e1e07dd and earlier converts HTTP(S) URLs in test report output to clickable links in an unsafe manner, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with Item/Configure permission.
CVE-2022-34176 Medium 2022-06-23 No exploit published Forecast only Jenkins JUnit Plugin 1119.va_a_5e9068da_d7 and earlier does not escape descriptions of test results, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with Run/Update permission.
CVE-2020-15250 Medium 2020-10-12 Protected by Waratek No public exploit In JUnit4 from version 4.7 and before 4.13.1, the test rule TemporaryFolder contains a local information disclosure vulnerability. On Unix like systems, the system's temporary directory is shared between all users on that system. Because of this, when files and directories are written into this directory they are, by default, readable by other users on that same system. This vulnerability does not allow other users to overwrite the contents of these directories or files. This is purely an information disclosure vulnerability. This vulnerability impacts you if the JUnit tests write sensitive information, like API keys or passwords, into the temporary folder, and the JUnit tests execute in an environment where the OS has other untrusted users. Because certain JDK file system APIs were only added in JDK 1.7, this this fix is dependent upon the version of the JDK you are using. For Java 1.7 and higher users: this vulnerability is fixed in 4.13.1. For Java 1.6 and lower users: no patch is available, you must use the workaround below. If you are unable to patch, or are stuck running on Java 1.6, specifying the `java.io.tmpdir` system environment variable to a directory that is exclusively owned by the executing user will fix this vulnerability. For more information, including an example of vulnerable code, see the referenced GitHub Security Advisory.
CVE-2018-1000411 Medium 2019-01-09 No exploit published No public exploit A cross-site request forgery vulnerability exists in Jenkins JUnit Plugin 1.25 and earlier in TestObject.java that allows setting the description of a test result.
CVE-2018-1000056 High 2018-02-09 Protected by Waratek No public exploit Jenkins JUnit Plugin 1.23 and earlier processes XML external entities in files it parses as part of the build process, allowing attackers with user permissions in Jenkins to extract secrets from the Jenkins master, perform server-side request forgery, or denial-of-service attacks.