chore(findings): opensource/apache/activemq
Summary
opensource/apache/activemq has 43 new findings discovered during continuous monitoring.
id | source | severity | package |
---|---|---|---|
CVE-2023-36479 | Anchore CVE | Medium | jetty-xml-9.4.50.v20221201 |
CVE-2023-41900 | Anchore CVE | Medium | jetty-rewrite-9.4.50.v20221201 |
CVE-2023-40167 | Anchore CVE | Medium | jetty-servlet-9.4.50.v20221201 |
CVE-2023-41900 | Anchore CVE | Medium | jetty-webapp-9.4.50.v20221201 |
CVE-2023-41900 | Anchore CVE | Medium | jetty-io-9.4.50.v20221201 |
CVE-2023-36479 | Anchore CVE | Medium | jetty-http-9.4.50.v20221201 |
CVE-2023-41900 | Anchore CVE | Medium | jetty-continuation-9.4.50.v20221201 |
CVE-2023-36479 | Anchore CVE | Medium | jetty-io-9.4.50.v20221201 |
CVE-2023-36479 | Anchore CVE | Medium | jetty-servlet-9.4.50.v20221201 |
CVE-2023-41900 | Anchore CVE | Medium | jetty-servlet-9.4.50.v20221201 |
CVE-2023-41900 | Anchore CVE | Medium | jetty-util-9.4.50.v20221201 |
CVE-2023-41900 | Anchore CVE | Medium | jetty-security-9.4.50.v20221201 |
CVE-2023-40167 | Anchore CVE | Medium | jetty-annotations-9.4.50.v20221201 |
CVE-2023-41900 | Anchore CVE | Medium | jetty-http-9.4.50.v20221201 |
CVE-2023-40167 | Anchore CVE | Medium | jetty-server-9.4.50.v20221201 |
CVE-2023-36479 | Anchore CVE | Medium | jetty-rewrite-9.4.50.v20221201 |
CVE-2023-36479 | Anchore CVE | Medium | jetty-webapp-9.4.50.v20221201 |
CVE-2023-40167 | Anchore CVE | Medium | jetty-security-9.4.50.v20221201 |
CVE-2023-41900 | Anchore CVE | Medium | jetty-server-9.4.50.v20221201 |
CVE-2023-41900 | Anchore CVE | Medium | jetty-xml-9.4.50.v20221201 |
CVE-2023-36479 | Anchore CVE | Medium | jetty-util-9.4.50.v20221201 |
CVE-2023-40167 | Anchore CVE | Medium | jetty-xml-9.4.50.v20221201 |
CVE-2023-40167 | Anchore CVE | Medium | jetty-plus-9.4.50.v20221201 |
CVE-2023-40167 | Anchore CVE | Medium | jetty-webapp-9.4.50.v20221201 |
CVE-2023-40167 | Anchore CVE | Medium | jetty-io-9.4.50.v20221201 |
CVE-2023-40167 | Anchore CVE | Medium | jetty-continuation-9.4.50.v20221201 |
CVE-2023-36479 | Anchore CVE | Medium | jetty-server-9.4.50.v20221201 |
CVE-2023-41900 | Anchore CVE | Medium | jetty-plus-9.4.50.v20221201 |
CVE-2023-36479 | Anchore CVE | Medium | jetty-continuation-9.4.50.v20221201 |
CVE-2023-36479 | Anchore CVE | Medium | jetty-annotations-9.4.50.v20221201 |
CVE-2023-36479 | Anchore CVE | Medium | jetty-plus-9.4.50.v20221201 |
CVE-2023-36479 | Anchore CVE | Medium | jetty-security-9.4.50.v20221201 |
CVE-2023-40167 | Anchore CVE | Medium | jetty-util-9.4.50.v20221201 |
CVE-2023-40167 | Anchore CVE | Medium | jetty-rewrite-9.4.50.v20221201 |
CVE-2023-41900 | Anchore CVE | Medium | jetty-annotations-9.4.50.v20221201 |
CVE-2023-2004 | Anchore CVE | Low | java-11-openjdk-headless-1:11.0.21.0.9-2.el8 |
GHSA-wgh7-54f2-x98r | Anchore CVE | High | jetty-http-9.4.50.v20221201 |
CVE-2022-33068 | Anchore CVE | Medium | java-11-openjdk-headless-1:11.0.21.0.9-2.el8 |
CVE-2023-40167 | Twistlock CVE | Medium | org.eclipse.jetty_jetty-io-9.4.50 |
CVE-2023-41900 | Twistlock CVE | Medium | org.eclipse.jetty_jetty-io-9.4.50 |
CVE-2023-36479 | Twistlock CVE | Medium | org.eclipse.jetty_jetty-io-9.4.50 |
CVE-2022-33068 | Twistlock CVE | Medium | java-11-openjdk-headless-11.0.21.0.9-2.el8 |
CVE-2022-3857 | Twistlock CVE | Low | java-11-openjdk-headless-11.0.21.0.9-2.el8 |
VAT: https://vat.dso.mil/vat/image?imageName=opensource/apache/activemq&tag=5.17.4&branch=master
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=opensource/apache/activemq&tag=5.17.4&branch=master
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
Verification
label 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 theVerification
label.
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.