UNCLASSIFIED - NO CUI

chore(findings): opensource/php/php73-composer-pear

Summary

opensource/php/php73-composer-pear has 6 new findings discovered during continuous monitoring.

More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=opensource/php/php73-composer-pear&tag=7.3.33&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
a98cf0855d75559fa066ce482f188a61 Anchore Compliance Low N/A N/A
8610d51e59f034d7551016b149f94d1b Anchore Compliance Low N/A N/A
84a8237ac2baee277a05a73dd2baecab Anchore Compliance Low N/A N/A
59e97d78f5482b9bbc0c5f30118f4b1b Anchore Compliance Low N/A N/A
54bc816e0bc5e1545b1896b69c612962 Anchore Compliance Low N/A N/A
025d7a1436e250cb601e0b2428d790f4 Anchore Compliance Low N/A N/A

More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=opensource/php/php73-composer-pear&tag=7.3.33&branch=master

Novel Tidelift Findings (Experimental)

opensource/php/php73-composer-pear has 13 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-2016-5699 6.1 urllib3-1.24.2 Its unlikely for an attacker to control URLs. Reject URLs with rn or encode those characters. 0.10221 false
CVE-2019-9740 6.1 urllib3-1.24.2 Its unlikely for an attacker to control the URL youre fetching. 0.06376 N/A
CVE-2023-32681 6.1 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.04731 false
CVE-2019-11324 7.5 urllib3-1.24.2 cacerts is a commonly used parameter. 0.01379 N/A
CVE-2021-33503 7.5 urllib3-1.24.2 Attackers dont usually control the URLs that urllib3 fetches. Its possible but inconvenient to filter URLs with many . 0.00863 N/A
CVE-2019-11236 6.1 urllib3-1.24.2 Its unlikely for an attacker to control an URL. Reject queries with rn or encode those characters. 0.00636 N/A
CVE-2023-43804 8.1 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.00554 false
CVE-2019-9947 6.1 urllib3-1.24.2 Its unlikely for an attacker to control an URL. Reject URLs with rn or encode those characters. 0.00402 N/A
CVE-2022-40897 7.5 setuptools-39.2.0 Code path is deprecated. 0.00318 N/A
CVE-2024-6345 8.8 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-2020-26137 6.5 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.00215 N/A
CVE-2023-45803 4.2 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.00062 false
CVE-2024-37891 4.4 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

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.