chore(findings): opensource/odoo/odoo
Summary
opensource/odoo/odoo has 22 new findings discovered during continuous monitoring.
id | source | severity | package |
---|---|---|---|
8d071a1f9bc914efeaecc7e725707983 | Anchore Compliance | Low | |
CVE-2024-26922 | Anchore CVE | Low | linux-libc-dev-5.10.209-2 |
CVE-2024-26925 | Anchore CVE | Low | linux-libc-dev-5.10.209-2 |
CVE-2024-26923 | Anchore CVE | Low | linux-libc-dev-5.10.209-2 |
CVE-2024-26924 | Anchore CVE | Low | linux-libc-dev-5.10.209-2 |
CVE-2024-26926 | Anchore CVE | Low | linux-libc-dev-5.10.209-2 |
CVE-2024-33600 | Anchore CVE | Low | libc-bin-2.31-13+deb11u9 |
CVE-2024-33602 | Anchore CVE | Low | libc-dev-bin-2.31-13+deb11u9 |
CVE-2024-33599 | Anchore CVE | Low | libc6-2.31-13+deb11u9 |
CVE-2024-33601 | Anchore CVE | Low | libc-dev-bin-2.31-13+deb11u9 |
CVE-2024-33600 | Anchore CVE | Low | libc6-dev-2.31-13+deb11u9 |
CVE-2024-33601 | Anchore CVE | Low | libc-bin-2.31-13+deb11u9 |
CVE-2024-33602 | Anchore CVE | Low | libc-bin-2.31-13+deb11u9 |
CVE-2024-33599 | Anchore CVE | Low | libc6-dev-2.31-13+deb11u9 |
CVE-2024-33601 | Anchore CVE | Low | libc6-dev-2.31-13+deb11u9 |
CVE-2024-33601 | Anchore CVE | Low | libc6-2.31-13+deb11u9 |
CVE-2024-33600 | Anchore CVE | Low | libc6-2.31-13+deb11u9 |
CVE-2024-33600 | Anchore CVE | Low | libc-dev-bin-2.31-13+deb11u9 |
CVE-2024-33602 | Anchore CVE | Low | libc6-dev-2.31-13+deb11u9 |
CVE-2024-33602 | Anchore CVE | Low | libc6-2.31-13+deb11u9 |
CVE-2024-33599 | Anchore CVE | Low | libc-bin-2.31-13+deb11u9 |
CVE-2024-33599 | Anchore CVE | Low | libc-dev-bin-2.31-13+deb11u9 |
VAT: https://vat.dso.mil/vat/image?imageName=opensource/odoo/odoo&tag=17.0&branch=master
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=opensource/odoo/odoo&tag=17.0&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.