Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update dependency org.testng:testng to v7.5.1 [SECURITY] #170

Merged
merged 1 commit into from
Jul 14, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 7, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
org.testng:testng (source) 7.5 -> 7.5.1 age adoption passing confidence

GitHub Vulnerability Alerts

CVE-2022-4065

Impact

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.

Patches

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]((https://github.com/cbeust/testng/releases/tag/7.5.1) for Java 8 projects.

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.

Release Notes

testng-team/testng (org.testng:testng)

v7.5.1: TestNG v7.5.1

Compare Source

What's Changed

New Contributors

Full Changelog: testng-team/testng@7.5...7.5.1


Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/maven-org.testng-testng-vulnerability branch 2 times, most recently from 0e12fee to c6115e4 Compare May 16, 2024 21:13
@renovate renovate bot force-pushed the renovate/maven-org.testng-testng-vulnerability branch from c6115e4 to 4c19059 Compare June 13, 2024 09:30
@renovate renovate bot force-pushed the renovate/maven-org.testng-testng-vulnerability branch 11 times, most recently from f9996db to fa4aa5f Compare July 14, 2024 13:41
@renovate renovate bot force-pushed the renovate/maven-org.testng-testng-vulnerability branch from fa4aa5f to eea4f12 Compare July 14, 2024 23:11
@diemol diemol merged commit 71cd04e into main Jul 14, 2024
2 checks passed
@diemol diemol deleted the renovate/maven-org.testng-testng-vulnerability branch July 14, 2024 23:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant