chore(findings): opensource/postgres/postgresql
Summary
opensource/postgres/postgresql has 53 new findings discovered during continuous monitoring.
id | source | severity | package |
---|---|---|---|
CVE-2024-33600 | Anchore CVE | Medium | glibc-langpack-en-2.34-100.el9 |
CVE-2024-33601 | Anchore CVE | Low | glibc-langpack-en-2.34-100.el9 |
CVE-2024-33599 | Anchore CVE | High | glibc-langpack-en-2.34-100.el9 |
CVE-2024-2961 | Anchore CVE | High | glibc-langpack-en-2.34-100.el9 |
CVE-2024-33602 | Anchore CVE | Low | glibc-langpack-en-2.34-100.el9 |
CVE-2022-41717 | Anchore CVE | Medium | stdlib-go1.18.2 |
CVE-2023-45287 | Anchore CVE | High | stdlib-go1.18.2 |
CVE-2023-24539 | Anchore CVE | High | stdlib-go1.18.2 |
CVE-2022-1705 | Anchore CVE | Medium | stdlib-go1.18.2 |
CVE-2022-41725 | Anchore CVE | High | stdlib-go1.18.2 |
CVE-2022-30633 | Anchore CVE | High | stdlib-go1.18.2 |
CVE-2022-30580 | Anchore CVE | High | stdlib-go1.18.2 |
CVE-2022-2879 | Anchore CVE | High | stdlib-go1.18.2 |
CVE-2022-41715 | Anchore CVE | High | stdlib-go1.18.2 |
CVE-2023-29404 | Anchore CVE | Critical | stdlib-go1.18.2 |
CVE-2023-24538 | Anchore CVE | Critical | stdlib-go1.18.2 |
CVE-2022-27664 | Anchore CVE | High | stdlib-go1.18.2 |
CVE-2022-2880 | Anchore CVE | High | stdlib-go1.18.2 |
CVE-2023-24534 | Anchore CVE | High | stdlib-go1.18.2 |
CVE-2023-29405 | Anchore CVE | Critical | stdlib-go1.18.2 |
CVE-2023-29402 | Anchore CVE | Critical | stdlib-go1.18.2 |
CVE-2023-24537 | Anchore CVE | High | stdlib-go1.18.2 |
CVE-2022-1962 | Anchore CVE | Medium | stdlib-go1.18.2 |
CVE-2023-39319 | Anchore CVE | Medium | stdlib-go1.18.2 |
CVE-2023-29409 | Anchore CVE | Medium | stdlib-go1.18.2 |
CVE-2022-32148 | Anchore CVE | Medium | stdlib-go1.18.2 |
CVE-2022-29458 | Anchore CVE | Low | ncurses-6.2-10.20210508.el9 |
CVE-2022-41723 | Anchore CVE | High | stdlib-go1.18.2 |
CVE-2022-30630 | Anchore CVE | High | stdlib-go1.18.2 |
CVE-2023-39318 | Anchore CVE | Medium | stdlib-go1.18.2 |
CVE-2023-24532 | Anchore CVE | Medium | stdlib-go1.18.2 |
CVE-2023-24536 | Anchore CVE | High | stdlib-go1.18.2 |
CVE-2023-45285 | Anchore CVE | High | stdlib-go1.18.2 |
CVE-2023-44487 | Anchore CVE | High | stdlib-go1.18.2 |
CVE-2022-30632 | Anchore CVE | High | stdlib-go1.18.2 |
CVE-2023-29400 | Anchore CVE | High | stdlib-go1.18.2 |
CVE-2023-29403 | Anchore CVE | High | stdlib-go1.18.2 |
CVE-2022-28131 | Anchore CVE | High | stdlib-go1.18.2 |
CVE-2023-24540 | Anchore CVE | Critical | stdlib-go1.18.2 |
CVE-2023-45803 | Anchore CVE | Medium | python3-pip-wheel-21.2.3-8.el9 |
CVE-2022-30635 | Anchore CVE | High | stdlib-go1.18.2 |
CVE-2022-30629 | Anchore CVE | Low | stdlib-go1.18.2 |
CVE-2023-39323 | Anchore CVE | High | stdlib-go1.18.2 |
CVE-2022-32189 | Anchore CVE | High | stdlib-go1.18.2 |
CVE-2022-30631 | Anchore CVE | High | stdlib-go1.18.2 |
CVE-2023-39326 | Anchore CVE | Medium | stdlib-go1.18.2 |
CVE-2022-41724 | Anchore CVE | High | stdlib-go1.18.2 |
CVE-2023-29406 | Anchore CVE | Medium | stdlib-go1.18.2 |
CVE-2024-2961 | Twistlock CVE | Critical | glibc-langpack-en-2.34-100.el9 |
CVE-2024-33599 | Twistlock CVE | Critical | glibc-langpack-en-2.34-100.el9 |
CVE-2024-33600 | Twistlock CVE | Medium | glibc-langpack-en-2.34-100.el9 |
CVE-2024-33602 | Twistlock CVE | Low | glibc-langpack-en-2.34-100.el9 |
CVE-2024-33601 | Twistlock CVE | Low | glibc-langpack-en-2.34-100.el9 |
VAT: https://vat.dso.mil/vat/image?imageName=opensource/postgres/postgresql&tag=14.11&branch=master
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=opensource/postgres/postgresql&tag=14.11&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.