chore(findings): opensource/apache/tomcat8-openjdk8

CHORE_TOKEN
2025-08-14T18:28:15Z

## Summary

opensource/apache/tomcat8-openjdk8 has 8 new findings discovered during continuous monitoring.

More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=opensource/apache/tomcat8-openjdk8&tag=8.5.100&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-2024-34750 | Twistlock CVE | High | tomcat-coyote-8.5.100 | | | 0.18312 | false
CVE-2025-31650 | Twistlock CVE | Medium | tomcat-coyote-8.5.100 | | | 0.00738 | false
CVE-2025-53506 | Twistlock CVE | Medium | tomcat-coyote-8.5.100 | | | 0.00218 | false
GHSA-wm9w-rjj3-j356 | Anchore CVE | High | tomcat-coyote-8.5.100 | | | N/A | N/A
GHSA-7jqf-v358-p8g7 | Anchore CVE | High | tomcat-util-8.5.100 | | | N/A | N/A
GHSA-4j3c-42xv-3f84 | Anchore CVE | Medium | tomcat-util-8.5.100 | | | N/A | N/A
GHSA-3p2h-wqq4-wf4h | Anchore CVE | Medium | tomcat-coyote-8.5.100 | | | N/A | N/A
GHSA-25xr-qj8w-c4vf | Anchore CVE | Medium | tomcat-coyote-8.5.100 | | | N/A | N/A

More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=opensource/apache/tomcat8-openjdk8&tag=8.5.100&branch=master

### Novel Tidelift Findings (Experimental)

opensource/apache/tomcat8-openjdk8 has 20 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-2024-34750 | 7.5 | org.apache.tomcat:tomcat-coyote-8.5.100 | | | 0.18312 | false
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.10836 | false
CVE-2019-9740 | 6.1 | urllib3-1.24.2 | Its unlikely for an attacker to control the URL youre fetching. | | 0.09968 | false
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.06121 | false
CVE-2019-11324 | 7.5 | urllib3-1.24.2 | cacerts is a commonly used parameter. | | 0.01571 | 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.01376 | false
CVE-2024-38286 | 7.5 | org.apache.tomcat:tomcat-util-8.5.100 | | | 0.00960 | false
CVE-2025-31650 | 6.6 | org.apache.tomcat:tomcat-coyote-8.5.100 | | | 0.00738 | false
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 | false
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-2022-40897 | 7.5 | setuptools-39.2.0 | Code path is deprecated. | | 0.00318 | 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.00261 | 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.00245 | false
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-2025-53506 | 6.3 | org.apache.tomcat:tomcat-coyote-8.5.100 | | | 0.00218 | false
CVE-2025-52434 | 6.3 | org.apache.tomcat:tomcat-util-8.5.100 | | | 0.00200 | false
CVE-2025-47273 | 7.7 | setuptools-39.2.0 | | | 0.00139 | false
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-47081 | 5.3 | requests-2.20.0 | | | 0.00024 | false
CVE-2025-50182 | 5.3 | urllib3-1.24.2 | Pyodide is extremely rare configuration for users in production. | | 0.00011 | false

## Tasks

Contributor:
- [x] Provide justifications for findings in the [VAT](https://vat.dso.mil) ([docs](https://docs-ironbank.dso.mil/hardening/justifications/))
- [x] Apply the ~"Status::Verification" label to this issue and wait for feedback

Iron Bank:
- [x] 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.