chore(findings): opensource/jenkins/trmc-jenkins
Summary
opensource/jenkins/trmc-jenkins has 1 new findings discovered during continuous monitoring.
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=opensource/jenkins/trmc-jenkins&tag=2.504.1-lts&branch=master
EPSS (Exploit Prediction Scoring System) provides an estimate of the likelihood that a vulnerability will be exploited in the wild.
KEV (Known Exploited Vulnerabilities) indicates whether a vulnerability is actively being exploited according to CISA.
| id | source | severity | package | impact | workaround | epss_score | kev |
|---|---|---|---|---|---|---|---|
| GHSA-wxr5-93ph-8wr9 | Anchore CVE | High | commons-beanutils-1.9.4 | N/A | N/A |
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=opensource/jenkins/trmc-jenkins&tag=2.504.1-lts&branch=master
Novel Tidelift Findings (Experimental)
opensource/jenkins/trmc-jenkins has 29 novel Tidelift findings discovered during continuous monitoring.
NOTE: This table is for Iron Bank evaluation and testing purposes. No action required by vendors.
| id | cvss score | package | impact | workaround | epss_score | kev |
|---|---|---|---|---|---|---|
| CVE-2018-10237 | 5.9 | com.google.guava:guava-18.0 | 0.03259 | false | ||
| CVE-2018-8088 | 9.8 | org.slf4j:slf4j-api-1.7.25 | As far as we know, the vulberable constructor org.slf4j.ext.EventData class is called by org.apache.logging.log4jlog4jslf4jimpl log4j 2 module by the org.apache.logging.slf4j.EventDataConverter class. This class does not seem to be in wide use. | 0.00836 | N/A | |
| CVE-2023-34462 | 6.5 | io.netty:netty-handler-4.1.46.Final | Its relatively easy to trigger DoS and make the server suffer from unnecessarily high memory usage by leveraging this vulnerability. | You can fork the fixed SniHandler in newer Netty version instead of using the one provided by the old Netty version. Alternatively, you can simply disable SNI by removing SniHandler from your channel pipeline. | 0.00416 | false |
| CVE-2024-23076 | org.jfree:jfreechart-1.0.19 | 0.00398 | false | |||
| CVE-2024-30172 | 7.5 | org.bouncycastle:bcprov-jdk18on-1.77 | 0.00187 | false | ||
| CVE-2024-23077 | org.jfree:jfreechart-1.0.19 | 0.00186 | false | |||
| CVE-2021-37533 | 6.5 | commons-net:commons-net-3.6 | A malicious server can redirect the Commons Net code to use a different host, but the user has to connect to the malicious server in the first place. | 0.00177 | N/A | |
| CVE-2024-29857 | 7.5 | org.bouncycastle:bcprov-jdk18on-1.77 | 0.00148 | false | ||
| CVE-2024-22949 | org.jfree:jfreechart-1.0.19 | 0.00122 | false | |||
| CVE-2025-4949 | 6.8 | org.eclipse.jgit:org.eclipse.jgit-7.0.0.202409031743-r | 0.00107 | false | ||
| CVE-2023-3635 | 7.5 | com.squareup.okio:okio-1.17.2 | 0.00084 | false | ||
| CVE-2024-30171 | 5.9 | org.bouncycastle:bcprov-jdk18on-1.77 | 0.00081 | false | ||
| CVE-2024-34447 | 5.9 | org.bouncycastle:bcprov-jdk18on-1.77 | 0.00079 | false | ||
| CVE-2023-52070 | org.jfree:jfreechart-1.0.19 | 0.00079 | false | |||
| CVE-2024-38827 | 4.8 | org.springframework:spring-beans-5.3.25 | 0.00071 | false | ||
| CVE-2024-29025 | 5.3 | io.netty:netty-codec-http-4.1.79.Final | HttpPostRequestDecoder is vulnerable to this issue regardless of whether it is used as intended or not. | If HttpPostRequestDecoder is NOT used for handling file uploads, a user could limit the length of an HTTP POST request body to a small value, which will effectively reduce the theoretically possible maximum number of form fields a request body can contain. However, this workaround might not be feasible if a user needs to handle file uploads, which may not be possible to limit the request both length. | 0.00056 | false |
| CVE-2025-22233 | org.springframework:spring-context-6.2.5 | 0.00047 | false | |||
| CVE-2023-2976 | 7.1 | com.google.guava:guava-31.1-jre | 0.00042 | false | ||
| CVE-2023-2976 | 7.1 | com.google.guava:guava-18.0 | 0.00042 | false | ||
| CVE-2024-47535 | 5.5 | io.netty:netty-common-4.1.79.Final | An attacker must acquire the privilege to override the content of system files such as etcresolv.conf and procsys. Given such powerful superuserlevel privilege, I would imagine the attacker will not waste their time to trigger OOME using this vulnerability. | 0.00039 | false | |
| CVE-2024-47554 | 4.3 | commons-io:commons-io-2.11.0 | Either an application is using the class org.apache.commons.io.input.XmlStreamReader or it is not if the class is in use then attackers can craft malicious input to make the application vulnerable if that application accepts input to XmlStreamReader from the world at large. If an application can be relatively certain that its XmlStreamReader input can be trusted, the risk could be lowered from a vulnerability to a bug. | An application could mitigate this vulnerability by validating the input given to the class. | 0.00036 | false |
| CVE-2025-25193 | 5.5 | io.netty:netty-common-4.1.79.Final | This vulnerability can be triggered only when an attacker already has the write access to the filesystem. In addition, an attacker must create the offending file in the filesystem before the application is started. Therefore, Id say the risk is fairly low. | 0.00035 | false | |
| CVE-2023-0833 | 5.5 | com.squareup.okhttp3:okhttp-3.14.9 | 0.00033 | false | ||
| CVE-2023-35116 | 4.7 | com.fasterxml.jackson.core:jackson-databind-2.14.1 | 0.00015 | false | ||
| CVE-2020-36843 | 4.3 | net.i2p.crypto:eddsa-0.3.0 | 0.00009 | false | ||
| CVE-2020-8908 | 3.3 | com.google.guava:guava-31.1-jre | 0.00008 | N/A | ||
| CVE-2020-8908 | 3.3 | com.google.guava:guava-18.0 | 0.00008 | N/A | ||
| CVE-2025-48734 | 8.8 | commons-beanutils:commons-beanutils-1.10.1 | N/A | N/A | ||
| CVE-2025-48734 | 8.8 | commons-beanutils:commons-beanutils-1.9.4 | N/A | N/A |
Tasks
Contributor:
-
Provide justifications for findings in the VAT (docs) -
Apply the StatusVerification label to this issue and wait for feedback
Iron Bank:
-
Review findings and justifications
Note: If the above process is rejected for any reason, the
Verificationlabel will be removed and the issue will be sent back toOpen. Any comments will be listed in this issue for you to address. Once they have been addressed, you must re-add theVerificationlabel.
Questions?
Contact the Iron Bank team by commenting on this issue with your questions or concerns. If you do not receive a response, add /cc @ironbank-notifications/onboarding.
Additionally, Iron Bank hosts an AMA working session every Wednesday from 1630-1730EST to answer questions.