UNCLASSIFIED - NO CUI

Skip to content

chore(findings): confluentinc/cp-ksqldb-server

Summary

confluentinc/cp-ksqldb-server has 21 new findings discovered during continuous monitoring.

id source severity package
GHSA-599f-7c49-w659 Anchore CVE Critical commons-text-1.8
CVE-2022-3171 Twistlock CVE Medium com.google.protobuf_protobuf-java-3.19.4
CVE-2022-24823 Twistlock CVE Medium io.netty_netty-codec-http-4.1.72
CVE-2022-40152 Twistlock CVE Low com.fasterxml.woodstox_woodstox-core-6.2.7
CVE-2022-41854 Twistlock CVE Medium org.yaml_snakeyaml-1.30
CVE-2022-41854 Twistlock CVE Medium org.yaml_snakeyaml-1.27
CVE-2022-1471 Twistlock CVE Critical org.yaml_snakeyaml-1.30
CVE-2022-3509 Twistlock CVE High com.google.protobuf_protobuf-java-3.19.4
CVE-2022-41881 Twistlock CVE Medium io.netty_netty-codec-haproxy-4.1.79
CVE-2022-41915 Twistlock CVE Low io.netty_netty-codec-http-4.1.79
CVE-2022-41915 Twistlock CVE Low io.netty_netty-codec-http-4.1.72
GHSA-g5ww-5jh7-63cx Anchore CVE High protobuf-java-3.19.4
GHSA-hh82-3pmq-7frp Anchore CVE Low netty-codec-http-4.1.72.Final
GHSA-g5ww-5jh7-63cx Anchore CVE High protobuf-java-3.19.4
CVE-2022-41881 Twistlock CVE High io.netty_netty-codec-4.1.79
CVE-2022-41881 Twistlock CVE High io.netty_netty-all-4.1.79
CVE-2022-3510 Twistlock CVE High com.google.protobuf_protobuf-java-3.19.4
GHSA-4gg5-vx3j-xwc7 Anchore CVE High protobuf-java-3.19.4
GHSA-4gg5-vx3j-xwc7 Anchore CVE High protobuf-java-3.19.4
CVE-2022-41915 Twistlock CVE Medium io.netty_netty-all-4.1.79
CVE-2022-41915 Twistlock CVE Medium io.netty_netty-codec-4.1.79

VAT: https://vat.dso.mil/vat/image?imageName=confluentinc/cp-ksqldb-server&tag=7.1.4-1-ubi8&branch=master
More information can be found in the failed pipeline located here: https://repo1.dso.mil/dsop/confluent/confluentinc/cp-ksqldb-server-7.1.x/-/jobs/15080968

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 to Open. Any comments will be listed in this issue for you to address. Once they have been addressed, you must re-add the Approval 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.

Edited by Ghost User
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information