swagger-api / swagger-api/swagger-codegen
CVE-2022-4065 (High) detected in testng-6.9.6.jar
Nobody has claimed this yet.
- Dominant language
- Mustache
- Stars
- 17.8k
- Forks
- 6k
- PR merge metrics
- No merged PRs in 30d
Description
CVE-2022-4065 - High Severity Vulnerability
Vulnerable Library - testng-6.9.6.jar
Testing framework for Java
Library home page: http://github.com/cbeust/testng
Path to vulnerable library: /modules/swagger-generator/target/lib/testng-6.9.6.jar
Dependency Hierarchy:
- ❌ testng-6.9.6.jar (Vulnerable Library)
Found in HEAD commit: 4b7a8d7d7384aa6a27d6309c35ade0916edae7ed
Found in base branches: 3.0.0, master
Vulnerability Details
A vulnerability was found in cbeust testng. It has been declared as critical. 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. The attack can be launched remotely. The name of the patch is 9150736cd2c123a6a3b60e6193630859f9f0422b. It is recommended to apply a patch to fix this issue. The associated identifier of this vulnerability is VDB-214027.
Publish Date: 2022-11-19
URL: CVE-2022-4065
CVSS 3 Score Details (7.8)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
Suggested Fix
Type: Upgrade version
Release Date: 2022-11-19
Fix Resolution: org.testng:testng:7.7.0
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the dependency declaration that produces modules/swagger-generator/target/lib/testng-6.9.6.jar, using the reported HEAD commit and base branches as context. Upgrade org.testng:testng to 7.7.0, run the relevant swagger-generator build or tests, and verify that the vulnerable testng jar is no longer produced.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, security
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100