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

Log4J Security Risk in 5.4.3 #5618

Closed
asfimport opened this issue Jan 19, 2022 · 1 comment
Closed

Log4J Security Risk in 5.4.3 #5618

asfimport opened this issue Jan 19, 2022 · 1 comment

Comments

@asfimport
Copy link
Collaborator

Neeti (Bug 65808):
Hi Jmeter team,

We are using Jmeter for our project . This mail is regarding the security risk because of log4J . We were using Jmeter4.0 (planning to upgraded to JMeter 5.4.3 version) . But according to release notes still log4J security risk is there in 5.4.3.

We need following help from you:

  1. It would be helpful if we can get fix for this issue .
  2. We have found that latest version of JMeter 5.4.3 which have 2.17.0 Log4j Jar

But 2.17 is also having two direct vulnerabilities , Details of both slows that they are vulnerable .

In Maven repository(https://mvnrepository.com/artifact/org.apache.logging.log4j/log4j-core) , we have 2.17.1 version which shows no vulnerability , so can you please advice that can we use 2.17.1 jar with apache Jmeter 5.4.3 version . Is that supported if we do it and will resolve the threat of currently log4j.

Severity: normal
OS: All

Duplicated by:

@asfimport
Copy link
Collaborator Author

@FSchumacher (migrated from Bugzilla):
This bug has been marked as a duplicate of #5601

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant