chore(findings): opensource/goharbor/harbor-db
Summary
opensource/goharbor/harbor-db has 20 new findings discovered during continuous monitoring.
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=opensource/goharbor/harbor-db&tag=v2.12.0&branch=master
| id | source | severity | package | impact | workaround |
|---|---|---|---|---|---|
| CVE-2016-1841 | Twistlock CVE | Medium | libxslt-1.1.34-9.el9 | ||
| CVE-2019-18197 | Twistlock CVE | Medium | libxslt-1.1.34-9.el9 | ||
| CVE-2016-7415 | Twistlock CVE | Medium | icu-67.1-9.el9 | ||
| CVE-2016-4738 | Twistlock CVE | Medium | libxslt-1.1.34-9.el9 | ||
| CVE-2019-11068 | Twistlock CVE | Medium | libxslt-1.1.34-9.el9 | ||
| CVE-2015-8853 | Twistlock CVE | Medium | perl-5.32.1-481.el9 | ||
| CVE-2017-7867 | Twistlock CVE | Medium | icu-67.1-9.el9 | ||
| CVE-2016-2381 | Twistlock CVE | Medium | perl-5.32.1-481.el9 | ||
| CVE-2015-7995 | Twistlock CVE | Medium | libxslt-1.1.34-9.el9 | ||
| CVE-2016-4610 | Twistlock CVE | Medium | libxslt-1.1.34-9.el9 | ||
| CVE-2016-4609 | Twistlock CVE | Medium | libxslt-1.1.34-9.el9 | ||
| CVE-2016-4608 | Twistlock CVE | Medium | libxslt-1.1.34-9.el9 | ||
| CVE-2016-4607 | Twistlock CVE | Medium | libxslt-1.1.34-9.el9 | ||
| CVE-2016-1684 | Twistlock CVE | Medium | libxslt-1.1.34-9.el9 | ||
| CVE-2016-1683 | Twistlock CVE | Medium | libxslt-1.1.34-9.el9 | ||
| CVE-2019-13118 | Twistlock CVE | Low | libxslt-1.1.34-9.el9 | ||
| CVE-2019-13117 | Twistlock CVE | Low | libxslt-1.1.34-9.el9 | ||
| CVE-2015-9019 | Twistlock CVE | Low | libxslt-1.1.34-9.el9 | ||
| CVE-2016-6293 | Twistlock CVE | Low | icu-67.1-9.el9 | ||
| CVE-2015-3194 | Twistlock CVE | Low | openssl-3.2.2-6.el9_5 |
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=opensource/goharbor/harbor-db&tag=v2.12.0&branch=master
Novel Tidelift Findings (Experimental)
NOTE: This table is for Iron Bank evaluation and testing purposes. No action required by vendors.
| id | cvss score | package | impact | workaround |
|---|---|---|---|---|
| CVE-2022-40897 | 7.5 | pkg:pypi/setuptools@53.0.0 | Code path is deprecated. | |
| CVE-2024-6345 | 8.8 | pkg:pypi/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. |
| CVE-2024-3651 | 7.5 | pkg:pypi/idna@2.10 | ||
| CVE-2023-32681 | 6.1 | pkg:pypi/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. | |
| CVE-2024-35195 | 5.6 | pkg:pypi/requests@2.25.1 | ||
| CVE-2023-45803 | 4.2 | pkg:pypi/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. |
| CVE-2024-37891 | 4.4 | pkg:pypi/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. |
| CVE-2023-43804 | 7.4 | pkg:pypi/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. |
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.