chore(findings): opensource/odoo/odoo-enterprise
Summary
opensource/odoo/odoo-enterprise has 2 new findings discovered during continuous monitoring.
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=opensource/odoo/odoo-enterprise&tag=18.0&branch=master
| id | source | severity | package | impact | workaround |
|---|---|---|---|---|---|
| CVE-2024-56827 | Anchore CVE | Medium | libopenjp2-7-2.5.0-2ubuntu0.2 | ||
| CVE-2024-56826 | Anchore CVE | Medium | libopenjp2-7-2.5.0-2ubuntu0.2 |
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=opensource/odoo/odoo-enterprise&tag=18.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-25881 | 5.3 | pkg:npm/http-cache-semantics@4.1.0 | ||
| CVE-2023-36464 | 6.2 | pkg:pypi/pypdf2@2.12.1 | Handling untrusted PDFs is quite a common usecase of PyPDF, as is extracting text from them. | |
| CVE-2023-45133 | 9.4 | pkg:npm/%40babel/traverse@7.20.13 | ||
| CVE-2024-24758 | 3.9 | pkg:npm/undici@5.26.3 | ||
| CVE-2024-30261 | 2.6 | pkg:npm/undici@5.26.3 | ||
| CVE-2024-30260 | 3.9 | pkg:npm/undici@5.26.3 | ||
| CVE-2024-43788 | 6.4 | pkg:npm/webpack@5.76.1 | ||
| CVE-2021-43138 | 7.8 | pkg:npm/async@0.8.0 | ||
| CVE-2024-39249 | 7.5 | pkg:npm/async@0.8.0 | ||
| CVE-2024-39689 | 7.5 | pkg:pypi/certifi@2023.11.17 | ||
| CVE-2024-4068 | 7.5 | pkg:npm/braces@3.0.2 | ||
| CVE-2024-55565 | 4.3 | pkg:npm/nanoid@3.3.7 | It is very rare to allow users to define ID size | Check that user pass real number |
| CVE-2024-52595 | 7.7 | pkg:pypi/lxml-html-clean@0.1.1 | ||
| CVE-2024-35195 | 5.6 | pkg:pypi/requests@2.31.0 | ||
| CVE-2024-28863 | 6.5 | pkg:npm/tar@6.1.13 | ||
| CVE-2024-6345 | 8.8 | pkg:pypi/setuptools@68.1.2 | 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@3.6 | ||
| CVE-2024-28219 | 6.7 | pkg:pypi/pillow@10.2.0 | Unlikely that a user would allow an attacker to enter an arbitrary mode string | Do not allow provide modes longer than 8 characters. This should not impact functionality, as no modes are that long. |
| CVE-2023-50782 | 7.5 | pkg:pypi/cryptography@41.0.7 | ||
| CVE-2024-26130 | 7.5 | pkg:pypi/cryptography@41.0.7 | ||
| CVE-2024-55565 | 4.3 | pkg:npm/nanoid@4.0.2 | It is very rare to allow users to define ID size | Check that user pass real number |
| CVE-2024-34069 | 7.5 | pkg:pypi/werkzeug@3.0.1 | While anyone using the debugger is technically vulnerable, it requires developers to use the debugger from within an attackercontrolled domain, and for the attacker to guess a URL that will raise an exception and start a debugger. The debugger still requires the developer to enter the debugger pin to enable the vulnerability. Developers should never expect clicking a link on an unfamiliar domain to start their local project, and closing the window if it happens will prevent the vulnerability. | Disable the debuggers interactive features by passing useevalexFalse to runsimple. Do not interact with the debugger unless you navigate to it explicitly. |
| CVE-2024-49767 | 7.5 | pkg:pypi/werkzeug@3.0.1 | Assuming the other conditions listed are met, then it is possible to exploit this. | Configure Request.maxcontentlength. |
| CVE-2024-49766 | 6.3 | pkg:pypi/werkzeug@3.0.1 | Assuming the other conditions listed are met, this is exploitable. | |
| CVE-2024-29415 | 8.1 | pkg:npm/ip@2.0.0 | ||
| CVE-2024-22195 | 5.4 | pkg:pypi/jinja2@3.1.2 | This requires using a specific filter in an uncommon way. | Prefilter user input that you plan to pass as the keys. Values do not need to be filtered, as they are already escaped. |
| CVE-2024-34064 | 5.4 | pkg:pypi/jinja2@3.1.2 | This requires using a specific filter in an uncommon way. | Prefilter user input that you plan to pass as the keys. Values do not need to be filtered, as they are already escaped. |
| CVE-2024-56326 | 7.8 | pkg:pypi/jinja2@3.1.2 | 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. | |
| CVE-2024-56201 | 8.8 | pkg:pypi/jinja2@3.1.2 | 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. |
| CVE-2023-26115 | 5.3 | pkg:npm/word-wrap@1.2.3 | ||
| CVE-2024-37891 | 4.4 | pkg:pypi/urllib3@2.0.7 | 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. |
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 Ghost User