chore(findings): confluentinc/confluent-init-container

Summary

confluentinc/confluent-init-container has 14 new findings discovered during continuous monitoring.

Layer: confluentinc/cp-base-new:Q4_2024_jdk17 is EOL, please update if possible

More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=confluentinc/confluent-init-container&tag=2.9.4&branch=master

EPSS (Exploit Prediction Scoring System) provides an estimate of the likelihood that a vulnerability will be exploited in the wild.

KEV (Known Exploited Vulnerabilities) indicates whether a vulnerability is actively being exploited according to CISA.

id	source	severity	package	impact	workaround	epss_score	kev
CVE-2023-32681	Twistlock CVE	Medium	requests-2.20.0	Requires that deployment or integration of requests is being used to a connect to untrusted hosts b is connecting over HTTPS and c is using proxies to do so.		0.04611	false
CVE-2019-11236	Twistlock CVE	Medium	urllib3-1.24.2	Its unlikely for an attacker to control an URL.	Reject queries with rn or encode those characters.	0.00654	N/A
CVE-2023-43804	Twistlock CVE	High	urllib3-1.24.2	Usage of the Cookie header is rare with urllib3. This is more common and useful in browsers. Redirections to another origin are also not the common case.		0.00569	false
CVE-2022-40897	Twistlock CVE	Medium	setuptools-39.2.0	Code path is deprecated.		0.00318	N/A
CVE-2022-40897	Twistlock CVE	Medium	setuptools-50.3.2	Code path is deprecated.		0.00318	N/A
CVE-2020-26137	Twistlock CVE	Medium	urllib3-1.24.2	Its unlikely to use putrequest which is not documented as part of urllib3s API, but only inherited from http.client.		0.00234	N/A
CVE-2024-6345	Twistlock CVE	High	setuptools-39.2.0	Most users have migrated off of the code paths that are affected. The affected code paths are actively deprecated and planned for turn down. Only specialized and legacy workflows are affected.	Use recommended installers pip, uv, build, system package managers to install all packages from trusted indexes. If working with untrusted content in private indexes, consider scanning for malicious code in the package index pages.	0.00227	false
CVE-2024-6345	Twistlock CVE	High	setuptools-50.3.2	Most users have migrated off of the code paths that are affected. The affected code paths are actively deprecated and planned for turn down. Only specialized and legacy workflows are affected.	Use recommended installers pip, uv, build, system package managers to install all packages from trusted indexes. If working with untrusted content in private indexes, consider scanning for malicious code in the package index pages.	0.00227	false
CVE-2023-45803	Twistlock CVE	Medium	urllib3-1.24.2	No exploits from real world were reported	Disable redirects for services that you arent expecting to respond with redirects with redirectsFalse.Disable automatic redirects with redirectsFalse and handle 303 redirects manually by stripping the HTTP request body.	0.00056	false
CVE-2025-47268	Anchore CVE	Medium	iputils-20180629-11.el8			0.00051	false
CVE-2024-3651	Twistlock CVE	Medium	idna-2.5			0.00051	false
CVE-2024-37891	Twistlock CVE	Medium	urllib3-1.24.2	Theres no reason to set ProxyAuthorization without using urllib3s proxy support.	Using the ProxyAuthorization header with urllib3s ProxyManager. Disabling HTTP redirects using redirectsFalse when sending requests. Not using the ProxyAuthorization header.	0.00033	false
CVE-2024-35195	Twistlock CVE	Medium	requests-2.20.0			0.00018	false
GHSA-pvp8-3xj6-8c6x	Anchore CVE	Low	commons-configuration-1.10			N/A	N/A

More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=confluentinc/confluent-init-container&tag=2.9.4&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 to Open. Any comments will be listed in this issue for you to address. Once they have been addressed, you must re-add the Verification 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.