chore(findings): neo4j-enterprise/neo4j
Summary
neo4j-enterprise/neo4j has 23 new findings discovered during continuous monitoring.
id | source | severity | package |
---|---|---|---|
CVE-2009-5046 | Anchore CVE | Medium | servlet-api-4.0.6 |
CVE-2021-28169 | Anchore CVE | Medium | servlet-api-4.0.6 |
GHSA-5jpm-x58v-624v | Anchore CVE | Medium | netty-codec-http-4.1.101.Final |
CVE-2022-0529 | Anchore CVE | Low | unzip-6.0-46.el8 |
CVE-2023-44487 | Anchore CVE | High | servlet-api-4.0.6 |
CVE-2023-0466 | Anchore CVE | Low | openssl-1:1.1.1k-12.el8_9 |
CVE-2023-0464 | Anchore CVE | Low | openssl-1:1.1.1k-12.el8_9 |
CVE-2009-5045 | Anchore CVE | High | servlet-api-4.0.6 |
CVE-2021-4217 | Anchore CVE | Low | unzip-6.0-46.el8 |
CVE-2017-7656 | Anchore CVE | High | servlet-api-4.0.6 |
CVE-2020-27216 | Anchore CVE | High | servlet-api-4.0.6 |
CVE-2017-9735 | Anchore CVE | High | servlet-api-4.0.6 |
CVE-2022-2047 | Anchore CVE | Low | servlet-api-4.0.6 |
CVE-2023-2650 | Anchore CVE | Medium | openssl-1:1.1.1k-12.el8_9 |
CVE-2021-34428 | Anchore CVE | Low | servlet-api-4.0.6 |
CVE-2022-0530 | Anchore CVE | Low | unzip-6.0-46.el8 |
CVE-2017-7658 | Anchore CVE | Critical | servlet-api-4.0.6 |
CVE-2017-7657 | Anchore CVE | Critical | servlet-api-4.0.6 |
CVE-2023-0465 | Anchore CVE | Low | openssl-1:1.1.1k-12.el8_9 |
CVE-2022-2048 | Anchore CVE | High | servlet-api-4.0.6 |
CVE-2023-26048 | Anchore CVE | Medium | servlet-api-4.0.6 |
CVE-2024-0727 | Anchore CVE | Low | openssl-1:1.1.1k-12.el8_9 |
CVE-2023-26049 | Anchore CVE | Medium | servlet-api-4.0.6 |
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=neo4j-enterprise/neo4j&tag=5.19.0&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.