chore(findings): opensource/jupyter/jupyter_codeserver_proxy
Summary
opensource/jupyter/jupyter_codeserver_proxy has 17 new findings discovered during continuous monitoring.
Layer: opensource/python:v3.11.9 is EOL, please update if possible
Layer: redhat/ubi/ubi9:9.4 is EOL, please update if possible
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=opensource/jupyter/jupyter_codeserver_proxy&tag=4.90.3-ae.1&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-12905 | Twistlock CVE | High | tar-fs-2.1.1 | Really depends on use. Most uses of tarfs use the packaging aspect. Normally if you use the extracting aspect you are also considering things like file limits already. | patches exist for all major release lines. if still unable to update, use a sandboxed directory or switch to tarstream to parse it yourself. | 0.00697 | false |
| CVE-2024-42367 | Anchore CVE | Medium | aiohttp-3.9.5 | Requires using static routes via aiohttp not recommended practice and some way for an attacker to get a symlink into the servers static directory. | Use a reverse proxy or ensure that symlinks cant be put into the static directory by users. | 0.00267 | false |
| CVE-2024-52304 | Twistlock CVE | Medium | aiohttp-3.9.5 | Most users do not use the Python parser. | Use the default C parser. | 0.00168 | false |
| CVE-2024-45296 | Twistlock CVE | High | path-to-regexp-3.2.0 | Its unlikely you are using routes that match the required characteristics, overwhelming majority of user paths stick with foobar or foo.bar. | Provide a manual regular expression to the second parameter that does not match the prefixed text. | 0.00167 | false |
| CVE-2025-48387 | Twistlock CVE | High | tar-fs-2.1.1 | If you are extracting untrusted tarballs you are affected and should upgrade. | Patch releases out for ALL release lines, so just update to latest patch, likely your npm already does this, you might need to bump your lock file if you use that. | 0.00110 | false |
| CVE-2024-4067 | Twistlock CVE | Medium | micromatch-4.0.5 | 0.00105 | false | ||
| CVE-2024-43800 | Twistlock CVE | Medium | serve-static-2.0.0-beta.2 | Users who are already validating and sanitizing their inputs as expected are highly unlikely to be impacted. | Validate and sanitize user input before passing it to this method. | 0.00073 | false |
| CVE-2024-47764 | Twistlock CVE | Low | cookie-0.4.0 | 0.00069 | false | ||
| CVE-2024-47764 | Twistlock CVE | Low | cookie-0.4.1 | 0.00069 | false | ||
| CVE-2024-47764 | Twistlock CVE | Low | cookie-0.6.0 | 0.00069 | false | ||
| CVE-2025-27789 | Twistlock CVE | Medium | @babel/runtime-7.23.2 | Its only if you are passing untrusted inputs to the second argument of RegExp.prototype.replace, which is a rare thing to do | 0.00050 | false | |
| CVE-2025-47269 | Twistlock CVE | High | code-server-4.90.3 | 0.00048 | false | ||
| CVE-2025-53643 | Twistlock CVE | Low | aiohttp-3.9.5 | If the above conditions are met which is already unlikely, they are affected. | 0.00044 | false | |
| CVE-2025-5889 | Twistlock CVE | Low | brace-expansion-1.1.11 | Im mirroring the CVE severity assessment here. | Sanitize strings being passed to the function so that they dont contain many , in a row. | 0.00022 | false |
| CVE-2025-7339 | Twistlock CVE | Low | on-headers-1.0.2 | 0.00006 | false | ||
| GHSA-9548-qrrj-x5pj | Anchore CVE | Low | aiohttp-3.9.5 | N/A | N/A | ||
| GHSA-8495-4g3g-x7pr | Anchore CVE | Medium | aiohttp-3.9.5 | N/A | N/A |
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=opensource/jupyter/jupyter_codeserver_proxy&tag=4.90.3-ae.1&branch=master
Novel Tidelift Findings (Experimental)
opensource/jupyter/jupyter_codeserver_proxy has 23 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-6345 | 8.8 | setuptools-53.0.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.09839 | 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.06277 | false | |
| CVE-2018-14041 | 6.1 | bootstrap-3.4.1 | 0.04647 | false | ||
| CVE-2020-7729 | 7.1 | grunt-1.0.0 | 0.02395 | false | ||
| CVE-2018-14042 | 6.1 | bootstrap-3.4.1 | 0.01122 | false | ||
| CVE-2018-14040 | 6.1 | bootstrap-3.4.1 | 0.01006 | false | ||
| CVE-2018-7206 | 8.8 | jupyterhub-4.1.5 | 0.00686 | false | ||
| CVE-2023-43804 | 8.1 | urllib3-1.26.5 | 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.00472 | false | |
| CVE-2024-3651 | 7.5 | idna-2.10 | 0.00338 | false | ||
| CVE-2022-40897 | 7.5 | setuptools-53.0.0 | Code path is deprecated. | 0.00318 | false | |
| CVE-2024-37891 | 4.4 | urllib3-1.26.5 | 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.00193 | false |
| CVE-2022-1537 | 7.0 | grunt-1.0.0 | 0.00182 | false | ||
| CVE-2020-7788 | 9.8 | ini-1.0.0 | 0.00153 | false | ||
| CVE-2025-47273 | 7.7 | setuptools-53.0.0 | 0.00139 | false | ||
| CVE-2024-21538 | 7.5 | cross-spawn-7.0.3 | 0.00109 | false | ||
| CVE-2022-0436 | 5.5 | grunt-1.0.0 | 0.00109 | false | ||
| CVE-2024-43796 | 4.7 | express-5.0.0-beta.3 | A successful exploitation of this vector requires the following1. The attacker MUST control the input to response.redirect2. express MUST NOT redirect before the template appears3. the browser MUST NOT complete redirection before4. the user MUST click on the link in the templateNote this exploitation requires a lot of work from the attacker, also the victim should use the links generated in the template, this require certain conditions browser rules, network, etc.... More details httpsgithub.comexpressjsexpresssecurityadvisoriesGHSAqw6hvgh9j6wx | Users are encouraged to upgrade to the patched version of express, but otherwise can workaround this issue by making sure any untrusted inputs are safe, ideally by validating them against an explicit allowlist | 0.00058 | 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.00055 | false |
| CVE-2024-6485 | 6.4 | bootstrap-3.4.1 | 0.00051 | false | ||
| CVE-2024-47081 | 5.3 | requests-2.25.1 | 0.00028 | false | ||
| CVE-2025-30370 | 7.4 | jupyterlab-git-0.50.0 | 0.00022 | false | ||
| CVE-2024-35195 | 5.6 | requests-2.25.1 | 0.00022 | false | ||
| CVE-2025-50182 | 5.3 | urllib3-1.26.5 | Pyodide is extremely rare configuration for users in production. | 0.00013 | 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
Verificationlabel will be removed and the issue will be sent back toOpen. Any comments will be listed in this issue for you to address. Once they have been addressed, you must re-add theVerificationlabel.
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 CHORE_TOKEN