CVE-2022-4065

TestNG is vulnerable to Path Traversal

Workaround

• Specify which tests to run when invoking TestNG by configuring them on the CLI or in the build tool controlling the run.
• Do not run tests with untrusted JARs on the classpath, this includes pull requests on open source projects.

Affected by this vulnerability is the function testngXmlExistsInJar of the file testng-core/src/main/java/org/testng/JarFileUtils.java of the component XML File Parser.

The manipulation leads to path traversal only for .xml, .yaml and .yml files by default. The attack implies running an unsafe test JAR. However since that JAR can also contain executable code itself, the path traversal is unlikely to be the main attack.

Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.

CVE-2022-4065 has a CVSS score of 7.8 (High). The vector is requires local access, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (7.5.1, 7.7.0); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

A patch is available in version 7.7.0 at commit 9150736cd2c123a6a3b60e6193630859f9f0422b. It is recommended to apply a patch to fix this issue. The patch was pushed into the master branch but no releases have yet been made with the patch included.

A backport of the fix is available in version 7.5.1 for Java 8 projects.

1. What is CVE-2022-4065? CVE-2022-4065 is a high-severity path traversal vulnerability in org.testng:testng (maven), affecting versions >= 6.13, < 7.5.1. It is fixed in 7.5.1, 7.7.0. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
2. How severe is CVE-2022-4065? CVE-2022-4065 has a CVSS score of 7.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of org.testng:testng are affected by CVE-2022-4065? org.testng:testng (maven) versions >= 6.13, < 7.5.1 is affected.
4. Is there a fix for CVE-2022-4065? Yes. CVE-2022-4065 is fixed in 7.5.1, 7.7.0. Upgrade to this version or later.
5. Is CVE-2022-4065 exploitable, and should I be worried? Whether CVE-2022-4065 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2022-4065 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2022-4065?
   • Upgrade org.testng:testng to 7.5.1 or later
   • Upgrade org.testng:testng to 7.7.0 or later