chore(findings): neo4j-enterprise/neo4j
Summary
neo4j-enterprise/neo4j has 14 new findings discovered during continuous monitoring.
id | source | severity | package |
---|---|---|---|
CVE-2022-3509 | Twistlock CVE | High | com.google.protobuf_protobuf-java-3.21.2 |
CVE-2022-41915 | Twistlock CVE | Low | io.netty_netty-codec-http-4.1.84 |
CVE-2022-41915 | Twistlock CVE | Low | io.netty_netty-codec-http-4.1.72 |
GHSA-hh82-3pmq-7frp | Anchore CVE | Low | netty-codec-http-4.1.72.Final |
GHSA-g5ww-5jh7-63cx | Anchore CVE | High | protobuf-java-3.21.2 |
GHSA-hh82-3pmq-7frp | Anchore CVE | Low | netty-codec-http-4.1.84.Final |
CVE-2022-41881 | Twistlock CVE | High | io.netty_netty-codec-4.1.79 |
CVE-2022-41881 | Twistlock CVE | High | io.netty_netty-codec-4.1.84 |
CVE-2022-3510 | Twistlock CVE | High | com.google.protobuf_protobuf-java-3.21.2 |
GHSA-4gg5-vx3j-xwc7 | Anchore CVE | High | protobuf-java-3.21.2 |
CVE-2022-41915 | Twistlock CVE | Medium | io.netty_netty-codec-4.1.84 |
CVE-2022-41915 | Twistlock CVE | Medium | io.netty_netty-codec-4.1.79 |
CVE-2022-40150 | Twistlock CVE | High | org.codehaus.jettison_jettison-1.5.1 |
GHSA-x27m-9w8j-5vcw | Anchore CVE | High | jettison-1.5.1 |
VAT: https://vat.dso.mil/vat/image?imageName=neo4j-enterprise/neo4j&tag=5.2.0&branch=master
More information can be found in the failed pipeline located here: https://repo1.dso.mil/dsop/neo4j-enterprise/neo4j/-/jobs/17000009
Tasks
Contributor:
-
Provide justifications for findings in the VAT (docs) -
Apply the ~"Hardening::Approval" label to this issue and wait for feedback
Iron Bank:
-
Review findings and justifications -
Send approval request to Authorizing Official -
Close issue after approval from Authorizing Official
Note: If the above approval process is rejected for any reason, the
Approval
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 theApproval
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.