Re: Log4j 2.17 Update

Hello, This CVE is not as critical as previous ones, it allows denial of service not to take control of server. since JMeter is not a server application but more a client tool, I don’t think there is an urgent need to release a new version. See: - https://snyk.io/blog/log4j-2-16-high-severity-vul

[GitHub] [jmeter] Chromico opened a new pull request #682: Update log4j to 2.17 to address CVE-2021-45105

Chromico opened a new pull request #682: URL: https://github.com/apache/jmeter/pull/682 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45105 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go

[GitHub] [jmeter] Chromico closed pull request #682: Update log4j to 2.17 to address CVE-2021-45105

Chromico closed pull request #682: URL: https://github.com/apache/jmeter/pull/682 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@

[GitHub] [jmeter] Chromico commented on pull request #682: Update log4j to 2.17 to address CVE-2021-45105

Chromico commented on pull request #682: URL: https://github.com/apache/jmeter/pull/682#issuecomment-997419735 Closed due to incomplete commits. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to t

[GitHub] [jmeter] Chromico opened a new pull request #683: Update log4j to 2.17 to address CVE-2021-45105.

Chromico opened a new pull request #683: URL: https://github.com/apache/jmeter/pull/683 log4j and log4j2 have been updated to address CVE-2021-45105. Learn more about the vulnerability here: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45105 -- This is an automated m

[GitHub] [jmeter] asfgit closed pull request #683: Update log4j to 2.17 to address CVE-2021-45105.

asfgit closed pull request #683: URL: https://github.com/apache/jmeter/pull/683 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@jm

[GitHub] [jmeter] FSchumacher commented on pull request #683: Update log4j to 2.17 to address CVE-2021-45105.

FSchumacher commented on pull request #683: URL: https://github.com/apache/jmeter/pull/683#issuecomment-997427519 Thanks for the PR. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific

Build failed in Jenkins: JMeter » JMeter-trunk #357

See Changes: [Felix Schumacher] Update log4j to 2.17.0 -- [...truncated 313.97 KB...] > Task :src:protocol:http:test 3.0sec, 22 completed, 0 faile

Jenkins build is back to normal : JMeter » JMeter-trunk #358

See

Jenkins build is back to normal : JMeter » JMeter-analysis #246

See

buildbot success in on jmeter-nightly

The Buildbot has detected a restored build on builder jmeter-nightly while building . Full details are available at: https://ci.apache.org/builders/jmeter-nightly/builds/2309 Buildbot URL: https://ci.apache.org/ Buildslave for this Build: bb_slave7_ubuntu Build Reason: The Nightly scheduler