UNCLASSIFIED - NO CUI

chore(findings): opensource/ceph/ceph-csi

Summary

opensource/ceph/ceph-csi has 5 new findings discovered during continuous monitoring.

More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=opensource/ceph/ceph-csi&tag=v3.15.0&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-2025-47907 Anchore CVE High stdlib-go1.24.3 0.00053 false
CVE-2025-47906 Anchore CVE Medium stdlib-go1.24.3 0.00022 false
CVE-2025-4673 Anchore CVE Medium stdlib-go1.24.3 0.00015 false
CVE-2025-22874 Anchore CVE High stdlib-go1.24.3 0.00013 false
CVE-2025-4674 Anchore CVE High stdlib-go1.24.3 0.00006 false

More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=opensource/ceph/ceph-csi&tag=v3.15.0&branch=master

Novel Tidelift Findings (Experimental)

opensource/ceph/ceph-csi has 18 novel Tidelift findings discovered during continuous monitoring.

NOTE: This table is for Iron Bank evaluation and testing purposes. No action required by vendors.

id cvss score package impact workaround epss_score kev
CVE-2022-29361 9.8 Werkzeug-2.0.3 0.28732 false
CVE-2024-39689 7.5 certifi-2023.5.7 0.21233 false
CVE-2023-32681 6.1 requests-2.25.1 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.06278 false
CVE-2024-6345 8.8 setuptools-69.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.04250 false
CVE-2023-38325 7.5 cryptography-36.0.1 0.01069 false
CVE-2022-2309 7.5 lxml-4.6.5 Requires processing specially forged content.Requires vulnerable code sequence on user side. 0.00659 false
CVE-2024-34997 7.5 joblib-1.4.2 0.00484 false
CVE-2023-23934 3.5 Werkzeug-2.0.3 If the conditions above are met and exploited. Avoid hosting next to untrusted subdomains, and avoid XSS vulnerabilities. 0.00242 false
CVE-2023-30861 7.5 Flask-2.0.3 Only when using permanent session cookies with a misconfigured caching proxy, as described above. Add the Vary cookie header using afterrequest, WSGI middleware, or HTTP server config. 0.00215 false
CVE-2025-47273 7.7 setuptools-69.2.0 0.00162 false
CVE-2021-22570 7.5 protobuf-3.14.0 0.00150 false
CVE-2022-1941 7.5 protobuf-3.14.0 0.00143 false
CVE-2024-37388 9.1 lxml-4.6.5 A lot of XML processing is either in or out, not passthrough.The issue has been resolved in lxml 5.x. Disable entity resolution in the parser with resolveentitiesFalse. 0.00119 false
CVE-2023-37920 9.8 certifi-2023.5.7 Many uses of Certifi use systemprovided CA certs. 0.00112 false
CVE-2024-47081 5.3 requests-2.25.1 0.00104 false
CVE-2025-9375 xmltodict-0.12.0 0.00081 false
CVE-2023-45803 4.2 urllib3-1.26.5 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-50182 5.3 urllib3-1.26.5 Pyodide is extremely rare configuration for users in production. 0.00013 false

Tasks

Contributor:

  • Apply the StatusReview label to this issue for a merge request review and wait for feedback

OR

  • Provide justifications for findings in the VAT (docs)
  • Apply the StatusVerification label to this issue for a VAT justifications review and wait for feedback

Iron Bank:

  • Review findings and justifications

Note: If the above process is rejected for any reason, the Review or Verification label will be removed and the issue will be sent back to To-Do. Any comments will be listed in this issue for you to address. Once they have been addressed, you must re-add the Review or 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.

Edited by Russell Huonder