chore(findings): opensource/jupyter/jupyter_codeserver_proxy
Summary
opensource/jupyter/jupyter_codeserver_proxy has 14 new findings discovered during continuous monitoring.
id | source | severity | package |
---|---|---|---|
GHSA-8qpw-xqxj-h4r2 | Anchore CVE | Medium | aiohttp-3.9.1 |
GHSA-5h86-8mv2-jq9f | Anchore CVE | Medium | aiohttp-3.9.1 |
GHSA-7gpw-8wmc-pm8g | Anchore CVE | Medium | aiohttp-3.9.1 |
GHSA-5m98-qgg9-wh84 | Anchore CVE | High | aiohttp-3.9.1 |
CVE-2024-23829 | Twistlock CVE | Medium | aiohttp-3.9.1 |
CVE-2024-23334 | Twistlock CVE | Medium | aiohttp-3.9.1 |
CVE-2024-27306 | Twistlock CVE | Medium | aiohttp-3.9.1 |
CVE-2024-30251 | Twistlock CVE | High | aiohttp-3.9.1 |
CVE-2024-28849 | Twistlock CVE | Medium | follow-redirects-1.15.4 |
CVE-2024-29041 | Twistlock CVE | Medium | express-5.0.0-alpha.8 |
CVE-2024-22017 | Twistlock CVE | Critical | nodejs-18.20.2-2.module+el9.4.0+21742+692df1ea |
CVE-2024-22017 | Twistlock CVE | Critical | nodejs-full-i18n-18.20.2-2.module+el9.4.0+21742+692df1ea |
CVE-2024-21891 | Twistlock CVE | Medium | nodejs-full-i18n-18.20.2-2.module+el9.4.0+21742+692df1ea |
CVE-2024-21891 | Twistlock CVE | Medium | nodejs-18.20.2-2.module+el9.4.0+21742+692df1ea |
VAT: https://vat.dso.mil/vat/image?imageName=opensource/jupyter/jupyter_codeserver_proxy&tag=4.22.0&branch=master
More information can be found in the failed pipeline located here: https://repo1.dso.mil/dsop/opensource/jupyter/jupyter_codeserver_proxy/-/jobs/23452349
Tasks
Contributor:
-
Provide justifications for findings in the VAT (docs) -
Apply the ~"Hardening::Verification" 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.