chore(findings): synopsys/codedx/codedx-docker-tomcat
Summary
synopsys/codedx/codedx-docker-tomcat has 19 new findings discovered during continuous monitoring.
| id | source | severity | package |
|---|---|---|---|
| CVE-2022-41881 | Twistlock CVE | High | io.netty_netty-codec-4.1.71 |
| CVE-2022-41881 | Twistlock CVE | High | io.netty_netty-all-4.1.74 |
| CVE-2022-41881 | Twistlock CVE | High | io.netty_netty-all-4.1.71 |
| CVE-2022-41881 | Twistlock CVE | High | io.netty_netty-codec-4.1.74 |
| CVE-2022-3510 | Twistlock CVE | High | com.google.protobuf_protobuf-java-3.7.1 |
| CVE-2022-3510 | Twistlock CVE | High | com.google.protobuf_protobuf-java-3.7.0 |
| CVE-2022-3510 | Twistlock CVE | High | com.google.protobuf_protobuf-java-3.16.1 |
| GHSA-4gg5-vx3j-xwc7 | Anchore CVE | High | protobuf-java-3.16.1 |
| GHSA-4gg5-vx3j-xwc7 | Anchore CVE | High | protobuf-java-3.7.1 |
| CVE-2022-41881 | Anchore CVE | High | netty-reactive-streams-2.0.4 |
| GHSA-4gg5-vx3j-xwc7 | Anchore CVE | High | protobuf-java-3.7.0 |
| CVE-2022-41915 | Twistlock CVE | Medium | io.netty_netty-all-4.1.71 |
| CVE-2022-41915 | Twistlock CVE | Medium | io.netty_netty-codec-4.1.71 |
| CVE-2022-41915 | Twistlock CVE | Medium | io.netty_netty-codec-4.1.74 |
| CVE-2022-41915 | Twistlock CVE | Medium | io.netty_netty-all-4.1.74 |
| GHSA-mjmj-j48q-9wg2 | Anchore CVE | High | snakeyaml-1.31 |
| GHSA-mjmj-j48q-9wg2 | Anchore CVE | High | snakeyaml-1.33 |
| GHSA-mjmj-j48q-9wg2 | Anchore CVE | High | snakeyaml-1.32 |
| CVE-2022-41915 | Anchore CVE | Medium | netty-reactive-streams-2.0.4 |
VAT: https://vat.dso.mil/vat/image?imageName=synopsys/codedx/codedx-docker-tomcat&tag=v2022.10.3&branch=master
More information can be found in the failed pipeline located here: https://repo1.dso.mil/dsop/synopsys/codedx/codedx-docker-tomcat/-/jobs/17158071
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
Approvallabel 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 theApprovallabel.
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.