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

JMeter plugin references log4j version vulnerable to exploits #645

Open
mgillian opened this issue Jun 13, 2023 · 0 comments
Open

JMeter plugin references log4j version vulnerable to exploits #645

mgillian opened this issue Jun 13, 2023 · 0 comments

Comments

@mgillian
Copy link
Contributor

Describe the bug
uPortal-start build.gradle references JMeter plugin net.foragerr.jmeter' version '1.1.0-4.0. As part of Gradle's caching process, this plugin loads log4j-core-2.17.0.jar and log4j-api-2.17.0.jar. Both of these jars are vulnerable to the log4j exploit.

To Reproduce
Steps to reproduce the behavior:

  1. Run ./gradlew tasks
  2. Go to ~/.gradle/caches`
  3. run find . -name log4j-*.*
  4. Both log4j jars will be listed.

Expected behavior
These jars are only used during gradle JMeter tasks, so there is no production risk. However, both of these jars are present on the server and may be flagged if you run monitoring software.

Platform:

  • uPortal Version: 5.0
  • OS:all
  • Browser all

Additional context
JMeter may be obsolete, so this plugin may be able to be deleted.
JMeter can be commented out of the code by commenting out the plugin in the Plugins block and commenting out the jmeter block in the build.gradle.
It is necessary to at least delete the two jars from the .gradle/caches folder once JMeter is either disabled or deleted. You can delete the entire .gradle/caches folder, and the next gradle task will rebuild it.

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

No branches or pull requests

1 participant