chore(findings): aiml/jupyter/jupyter_codeserver_proxy
Summary
aiml/jupyter/jupyter_codeserver_proxy has 99 new findings discovered during continuous monitoring.
Layer: opensource/jupyter/jupyter_codeserver_proxy:4.90.3 is EOL, please update if possible
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=aiml/jupyter/jupyter_codeserver_proxy&tag=4.90.3&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-39689 | Twistlock CVE | High | certifi-2024.6.2 | 0.21233 | false | ||
CVE-2021-31535 | Anchore CVE | High | libX11-common-1.7.0-11.el9 | 0.02601 | false | ||
CVE-2021-31535 | Anchore CVE | High | libX11-1.7.0-11.el9 | 0.02601 | false | ||
CVE-2021-31535 | Anchore CVE | High | libX11-xcb-1.7.0-11.el9 | 0.02601 | false | ||
CVE-2021-31535 | Twistlock CVE | Medium | libX11-1.7.0-11.el9 | 0.02601 | false | ||
CVE-2024-39700 | Twistlock CVE | Critical | jupyterlab-4.0.11 | 0.00852 | false | ||
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-49767 | Twistlock CVE | High | werkzeug-3.0.3 | Assuming the other conditions listed are met, then it is possible to exploit this. | Configure Request.maxcontentlength. | 0.00602 | false |
CVE-2024-52804 | Twistlock CVE | Low | tornado-6.4.1 | 0.00400 | 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-2022-0529 | Anchore CVE | Low | unzip-6.0-58.el9_5 | 0.00242 | false | ||
CVE-2022-0529 | Twistlock CVE | Low | unzip-6.0-58.el9_5 | 0.00242 | false | ||
CVE-2024-12797 | Twistlock CVE | Low | cryptography-42.0.8 | 0.00222 | false | ||
CVE-2022-41723 | Anchore CVE | Medium | git-lfs-3.6.1-2.el9_6 | 0.00188 | false | ||
CVE-2022-41723 | Twistlock CVE | Medium | git-lfs-3.6.1-2.el9_6 | 0.00188 | 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-2021-4217 | Anchore CVE | Low | unzip-6.0-58.el9_5 | 0.00148 | false | ||
CVE-2021-4217 | Twistlock CVE | Low | unzip-6.0-58.el9_5 | 0.00148 | false | ||
CVE-2025-47273 | Twistlock CVE | High | setuptools-70.1.1 | 0.00139 | false | ||
CVE-2022-0530 | Anchore CVE | Low | unzip-6.0-58.el9_5 | 0.00120 | false | ||
CVE-2022-0530 | Twistlock CVE | Low | unzip-6.0-58.el9_5 | 0.00120 | false | ||
CVE-2025-47287 | Twistlock CVE | High | tornado-6.4.1 | 0.00118 | false | ||
CVE-2023-29409 | Anchore CVE | Medium | git-lfs-3.6.1-2.el9_6 | 0.00112 | false | ||
CVE-2023-29409 | Twistlock CVE | Medium | git-lfs-3.6.1-2.el9_6 | 0.00112 | 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.6.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.4.0 | 0.00069 | false | ||
CVE-2023-24536 | Anchore CVE | Medium | git-lfs-3.6.1-2.el9_6 | 0.00066 | false | ||
CVE-2023-24536 | Twistlock CVE | Medium | git-lfs-3.6.1-2.el9_6 | 0.00066 | false | ||
CVE-2024-49766 | Twistlock CVE | Medium | werkzeug-3.0.3 | Assuming the other conditions listed are met, this is exploitable. | 0.00062 | false | |
CVE-2022-41725 | Anchore CVE | Medium | git-lfs-3.6.1-2.el9_6 | 0.00051 | false | ||
CVE-2022-41725 | Twistlock CVE | Medium | git-lfs-3.6.1-2.el9_6 | 0.00051 | 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-2023-24534 | Anchore CVE | Medium | git-lfs-3.6.1-2.el9_6 | 0.00045 | false | ||
CVE-2023-24534 | Twistlock CVE | Medium | git-lfs-3.6.1-2.el9_6 | 0.00045 | 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-2024-56326 | Twistlock CVE | Medium | jinja2-3.1.4 | This vulnerability impacts applications which execute untrusted templates. This is uncommon for web and other document rendering use cases, but may be common in deployment tools that allow third party plugins. | 0.00044 | false | |
CVE-2025-27516 | Twistlock CVE | Medium | jinja2-3.1.4 | This vulnerability impacts applications which execute untrusted templates. This is uncommon for web and other document rendering use cases, but may be common in deployment tools that allow third party plugins. | 0.00042 | false | |
CVE-2024-45336 | Anchore CVE | Medium | git-lfs-3.6.1-2.el9_6 | 0.00041 | false | ||
CVE-2024-45336 | Twistlock CVE | Medium | git-lfs-3.6.1-2.el9_6 | 0.00041 | false | ||
CVE-2024-8244 | Anchore CVE | Medium | git-lfs-3.6.1-2.el9_6 | 0.00036 | false | ||
CVE-2024-8244 | Twistlock CVE | Medium | git-lfs-3.6.1-2.el9_6 | 0.00036 | false | ||
CVE-2024-45341 | Anchore CVE | Low | git-lfs-3.6.1-2.el9_6 | 0.00032 | false | ||
CVE-2024-45341 | Twistlock CVE | Low | git-lfs-3.6.1-2.el9_6 | 0.00032 | false | ||
CVE-2025-7039 | Twistlock CVE | Low | glib2-2.68.4-16.el9_6.2 | 0.00029 | false | ||
CVE-2024-47081 | Twistlock CVE | Medium | requests-2.32.3 | 0.00028 | false | ||
CVE-2025-4565 | Twistlock CVE | High | protobuf-5.27.2 | 0.00025 | false | ||
CVE-2025-8941 | Anchore CVE | High | pam-1.5.1-26.el9_6 | 0.00024 | false | ||
CVE-2025-5889 | Twistlock CVE | Low | brace-expansion-2.0.1 | 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-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-2024-56201 | Twistlock CVE | Medium | jinja2-3.1.4 | This vulnerability impacts applications which execute untrusted templates where the template author can also choose the template filename. This is uncommon for web and other document rendering use cases, but may be common in deployment tools that allow third party plugins. | Check if any template filenames contain curly braces and . If so, and the braces enclose Python code, audit or remove those files. | 0.00021 | false |
CVE-2022-23806 | Twistlock CVE | Medium | git-lfs-3.6.1-2.el9_6 | 0.00020 | false | ||
CVE-2021-3782 | Anchore CVE | Medium | libwayland-server-1.21.0-1.el9 | 0.00020 | false | ||
CVE-2025-4673 | Anchore CVE | Medium | git-lfs-3.6.1-2.el9_6 | 0.00019 | false | ||
CVE-2025-4673 | Twistlock CVE | Medium | git-lfs-3.6.1-2.el9_6 | 0.00019 | false | ||
CVE-2022-41724 | Anchore CVE | Medium | git-lfs-3.6.1-2.el9_6 | 0.00016 | false | ||
CVE-2022-41724 | Twistlock CVE | Medium | git-lfs-3.6.1-2.el9_6 | 0.00016 | false | ||
CVE-2025-50181 | Twistlock CVE | Medium | urllib3-2.2.2 | Most users dont disable redirects on the PoolManager. | Set redirectsFalseredirects0 on the .request call instead of on the toplevel urllib3.PoolManager | 0.00015 | false |
CVE-2025-22870 | Anchore CVE | Medium | git-lfs-3.6.1-2.el9_6 | 0.00015 | false | ||
CVE-2025-22870 | Twistlock CVE | Medium | git-lfs-3.6.1-2.el9_6 | 0.00015 | false | ||
CVE-2025-30167 | Twistlock CVE | High | jupyter_core-5.7.2 | 0.00014 | false | ||
CVE-2025-50182 | Twistlock CVE | Medium | urllib3-2.2.2 | Pyodide is extremely rare configuration for users in production. | 0.00013 | false | |
CVE-2025-22866 | Anchore CVE | Medium | git-lfs-3.6.1-2.el9_6 | 0.00012 | false | ||
CVE-2025-22866 | Twistlock CVE | Medium | git-lfs-3.6.1-2.el9_6 | 0.00012 | false | ||
CVE-2025-7339 | Twistlock CVE | Low | on-headers-1.0.2 | 0.00006 | false | ||
CVE-2022-3555 | Anchore CVE | Low | libX11-xcb-1.7.0-11.el9 | N/A | false | ||
CVE-2022-3555 | Anchore CVE | Low | libX11-common-1.7.0-11.el9 | N/A | false | ||
CVE-2022-3555 | Anchore CVE | Low | libX11-1.7.0-11.el9 | N/A | false | ||
CVE-2022-3554 | Anchore CVE | Medium | libX11-xcb-1.7.0-11.el9 | N/A | false | ||
CVE-2022-3554 | Anchore CVE | Medium | libX11-1.7.0-11.el9 | N/A | false | ||
CVE-2022-3554 | Anchore CVE | Medium | libX11-common-1.7.0-11.el9 | N/A | false | ||
dd33f9ae335b0724372e0508851608ba | Anchore Compliance | Critical | N/A | N/A | |||
dca46c8cc6a3a34c7ad5f79aa304305f | Anchore Compliance | Low | N/A | N/A | |||
addbb93c22e9b0988b8b40392a4538cb | Anchore Compliance | Low | N/A | N/A | |||
GHSA-v6h2-p8h4-qcjw | Anchore CVE | Low | brace-expansion-2.0.1 | N/A | N/A | ||
GHSA-q34m-jh98-gwm2 | Anchore CVE | Medium | werkzeug-3.0.3 | N/A | N/A | ||
GHSA-q2x7-8rv6-6q7h | Anchore CVE | Medium | jinja2-3.1.4 | N/A | N/A | ||
GHSA-pq67-6m6q-mj2v | Anchore CVE | Medium | urllib3-2.2.2 | N/A | N/A | ||
GHSA-h4gh-qq45-vh27 | Twistlock CVE | Medium | cryptography-42.0.8 | N/A | N/A | ||
GHSA-h4gh-qq45-vh27 | Anchore CVE | Medium | cryptography-42.0.8 | N/A | N/A | ||
GHSA-gmj6-6f8f-6699 | Anchore CVE | Medium | jinja2-3.1.4 | N/A | N/A | ||
GHSA-f9vj-2wh5-fj8j | Anchore CVE | Medium | werkzeug-3.0.3 | N/A | N/A | ||
GHSA-cpwx-vrp4-4pq7 | Anchore CVE | Medium | jinja2-3.1.4 | N/A | N/A | ||
GHSA-9hjg-9r4m-mvj7 | Anchore CVE | Medium | requests-2.32.3 | N/A | N/A | ||
GHSA-9548-qrrj-x5pj | Anchore CVE | Low | aiohttp-3.9.5 | N/A | N/A | ||
GHSA-8w49-h785-mj3c | Anchore CVE | High | tornado-6.4.1 | N/A | N/A | ||
GHSA-8qvm-5x2c-j2w7 | Anchore CVE | High | protobuf-5.27.2 | N/A | N/A | ||
GHSA-8495-4g3g-x7pr | Anchore CVE | Medium | aiohttp-3.9.5 | N/A | N/A | ||
GHSA-7cx3-6m66-7c5m | Anchore CVE | High | tornado-6.4.1 | N/A | N/A | ||
GHSA-79v4-65xg-pq4g | Anchore CVE | Low | cryptography-42.0.8 | N/A | N/A | ||
GHSA-5rjg-fvgr-3xxf | Anchore CVE | High | setuptools-70.1.1 | N/A | N/A | ||
GHSA-48p4-8xcf-vxj5 | Anchore CVE | Medium | urllib3-2.2.2 | N/A | N/A | ||
GHSA-33p9-3p43-82vq | Anchore CVE | High | jupyter-core-5.7.2 | N/A | N/A | ||
GHSA-248v-346w-9cwc | Anchore CVE | Low | certifi-2024.6.2 | N/A | N/A |
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=aiml/jupyter/jupyter_codeserver_proxy&tag=4.90.3&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 toOpen
. Any comments will be listed in this issue for you to address. Once they have been addressed, you must re-add theVerification
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.