chore(findings): opensource/apache/tomee-openjdk8
Summary
opensource/apache/tomee-openjdk8 has 53 new findings discovered during continuous monitoring.
id | source | severity | package |
---|---|---|---|
GHSA-qmgx-j96g-4428 | Anchore CVE | Medium | cxf-core-3.5.7 |
CVE-2023-46589 | Anchore CVE | High | tomcat-api-9.0.82 |
CVE-2016-5425 | Anchore CVE | High | tomcat-coyote-9.0.82 |
CVE-2016-5425 | Anchore CVE | High | tomcat-api-9.0.82 |
CVE-2023-46589 | Anchore CVE | High | tomcat-i18n-es-9.0.82 |
CVE-2023-46589 | Anchore CVE | High | tomcat-i18n-pt-BR-9.0.82 |
CVE-2016-6325 | Anchore CVE | High | tomcat-coyote-9.0.82 |
CVE-2023-46589 | Anchore CVE | High | tomcat-i18n-de-9.0.82 |
CVE-2016-5425 | Anchore CVE | High | tomcat-websocket-9.0.82 |
CVE-2016-5425 | Anchore CVE | High | tomcat-i18n-ru-9.0.82 |
CVE-2016-6325 | Anchore CVE | High | tomcat-dbcp-9.0.82 |
CVE-2016-6325 | Anchore CVE | High | tomcat-i18n-cs-9.0.82 |
CVE-2016-6325 | Anchore CVE | High | tomcat-i18n-zh-CN-9.0.82 |
CVE-2016-5425 | Anchore CVE | High | tomcat-util-scan-9.0.82 |
CVE-2023-46589 | Anchore CVE | High | tomcat-i18n-ru-9.0.82 |
CVE-2016-6325 | Anchore CVE | High | tomcat-i18n-ja-9.0.82 |
GHSA-7w75-32cg-r6g2 | Anchore CVE | Medium | tomcat-coyote-9.0.82 |
CVE-2023-46589 | Anchore CVE | High | tomcat-i18n-cs-9.0.82 |
CVE-2016-6325 | Anchore CVE | High | tomcat-i18n-pt-BR-9.0.82 |
CVE-2023-46589 | Anchore CVE | High | tomcat-websocket-9.0.82 |
CVE-2016-5425 | Anchore CVE | High | tomcat-jni-9.0.82 |
CVE-2016-6325 | Anchore CVE | High | tomcat-util-scan-9.0.82 |
CVE-2016-6325 | Anchore CVE | High | tomcat-i18n-de-9.0.82 |
CVE-2016-6325 | Anchore CVE | High | tomcat-websocket-9.0.82 |
CVE-2023-46589 | Anchore CVE | High | tomcat-dbcp-9.0.82 |
CVE-2023-46589 | Anchore CVE | High | tomcat-i18n-ko-9.0.82 |
CVE-2016-6325 | Anchore CVE | High | tomcat-util-9.0.82 |
CVE-2016-6325 | Anchore CVE | High | tomcat-i18n-ko-9.0.82 |
CVE-2016-5425 | Anchore CVE | High | tomcat-i18n-de-9.0.82 |
CVE-2023-46589 | Anchore CVE | High | tomcat-jni-9.0.82 |
CVE-2016-5425 | Anchore CVE | High | tomcat-i18n-ja-9.0.82 |
CVE-2016-5425 | Anchore CVE | High | tomcat-i18n-cs-9.0.82 |
CVE-2016-6325 | Anchore CVE | High | tomcat-api-9.0.82 |
CVE-2016-6325 | Anchore CVE | High | tomcat-i18n-ru-9.0.82 |
CVE-2023-46589 | Anchore CVE | High | tomcat-coyote-9.0.82 |
CVE-2016-5425 | Anchore CVE | High | tomcat-i18n-fr-9.0.82 |
CVE-2016-5425 | Anchore CVE | High | tomcat-i18n-ko-9.0.82 |
CVE-2016-6325 | Anchore CVE | High | tomcat-jni-9.0.82 |
CVE-2023-46589 | Anchore CVE | High | tomcat-i18n-ja-9.0.82 |
CVE-2016-5425 | Anchore CVE | High | tomcat-i18n-zh-CN-9.0.82 |
CVE-2023-46589 | Anchore CVE | High | tomcat-i18n-zh-CN-9.0.82 |
CVE-2016-5425 | Anchore CVE | High | tomcat-i18n-es-9.0.82 |
GHSA-v682-8vv8-vpwr | Anchore CVE | Medium | tomcat-websocket-9.0.82 |
CVE-2016-6325 | Anchore CVE | High | tomcat-i18n-fr-9.0.82 |
CVE-2016-5425 | Anchore CVE | High | tomcat-i18n-pt-BR-9.0.82 |
CVE-2016-5425 | Anchore CVE | High | tomcat-util-9.0.82 |
CVE-2023-46589 | Anchore CVE | High | tomcat-util-9.0.82 |
CVE-2023-46589 | Anchore CVE | High | tomcat-i18n-fr-9.0.82 |
CVE-2016-5425 | Anchore CVE | High | tomcat-dbcp-9.0.82 |
GHSA-jw7r-rxff-gv24 | Anchore CVE | Medium | apache-mime4j-core-0.8.1 |
CVE-2023-46589 | Anchore CVE | High | tomcat-util-scan-9.0.82 |
CVE-2016-6325 | Anchore CVE | High | tomcat-i18n-es-9.0.82 |
CVE-2024-34447 | Twistlock CVE | Low | org.bouncycastle_bcprov-jdk15to18-1.76 |
VAT: https://vat.dso.mil/vat/image?imageName=opensource/apache/tomee-openjdk8&tag=8.0.16-jre8-plus&branch=master
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=opensource/apache/tomee-openjdk8&tag=8.0.16-jre8-plus&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.