chore(findings): enterprisedb/edb-postgres-advanced-16
Summary
enterprisedb/edb-postgres-advanced-16 has 72 new findings discovered during continuous monitoring.
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=enterprisedb/edb-postgres-advanced-16&tag=16.6.0&branch=master
id | source | severity | package | impact | workaround |
---|---|---|---|---|---|
PRISMA-2022-0168 | Twistlock CVE | High | pip-24.3.1 | ||
PRISMA-2022-0168 | Twistlock CVE | High | pip-22.3.1 | ||
CVE-2023-47038 | Twistlock CVE | Medium | perl-File-Path-2.15-2.el8 | ||
CVE-2023-47038 | Twistlock CVE | Medium | perl-Data-Dumper-2.167-399.el8 | ||
CVE-2023-47038 | Twistlock CVE | Medium | perl-Text-ParseWords-3.30-395.el8 | ||
CVE-2023-47038 | Twistlock CVE | Medium | perl-Exporter-5.72-396.el8 | ||
CVE-2023-47038 | Twistlock CVE | Medium | perl-Text-Tabs+Wrap-2013.0523-395.el8 | ||
CVE-2023-47038 | Twistlock CVE | Medium | perl-MIME-Base64-3.15-396.el8 | ||
CVE-2023-47038 | Twistlock CVE | Medium | perl-podlators-4.11-1.el8 | ||
CVE-2023-47038 | Twistlock CVE | Medium | perl-5.26.3-422.el8 | ||
CVE-2023-47038 | Twistlock CVE | Medium | perl-Digest-1.17-395.el8 | ||
CVE-2023-47038 | Twistlock CVE | Medium | perl-parent-0.237-1.el8 | ||
CVE-2023-47038 | Twistlock CVE | Medium | perl-Pod-Simple-3.35-395.el8 | ||
CVE-2023-47038 | Twistlock CVE | Medium | perl-Socket-2.027-3.el8 | ||
CVE-2023-47038 | Twistlock CVE | Medium | perl-Storable-3.11-3.el8 | ||
CVE-2023-47038 | Twistlock CVE | Medium | perl-Pod-Usage-1.69-395.el8 | ||
CVE-2023-47038 | Twistlock CVE | Medium | perl-Term-ANSIColor-4.06-396.el8 | ||
CVE-2023-47038 | Twistlock CVE | Medium | perl-Encode-2.97-3.el8 | ||
CVE-2023-47038 | Twistlock CVE | Medium | perl-HTTP-Tiny-0.074-3.el8 | ||
CVE-2023-47038 | Twistlock CVE | Medium | perl-libnet-3.11-3.el8 | ||
CVE-2023-47038 | Twistlock CVE | Medium | perl-File-Temp-0.230.600-1.el8 | ||
CVE-2023-47038 | Twistlock CVE | Medium | perl-Pod-Perldoc-3.28-396.el8 | ||
CVE-2023-47038 | Twistlock CVE | Medium | perl-Time-Local-1.280-1.el8 | ||
CVE-2023-47038 | Twistlock CVE | Medium | perl-Getopt-Long-2.50-4.el8 | ||
CVE-2023-47038 | Twistlock CVE | Medium | perl-PathTools-3.74-1.el8 | ||
CVE-2023-47038 | Twistlock CVE | Medium | perl-Carp-1.42-396.el8 | ||
CVE-2023-47038 | Twistlock CVE | Medium | perl-Term-Cap-1.17-395.el8 | ||
CVE-2023-47038 | Twistlock CVE | Medium | perl-Unicode-Normalize-1.25-396.el8 | ||
CVE-2023-47038 | Twistlock CVE | Medium | perl-Digest-MD5-2.55-396.el8 | ||
CVE-2023-47038 | Twistlock CVE | Medium | perl-threads-2.21-2.el8 | ||
CVE-2023-47038 | Twistlock CVE | Medium | perl-Pod-Escapes-1.07-395.el8 | ||
CVE-2023-47038 | Twistlock CVE | Medium | perl-constant-1.33-396.el8 | ||
CVE-2023-47038 | Twistlock CVE | Medium | perl-URI-1.73-3.el8 | ||
CVE-2023-47038 | Twistlock CVE | Medium | perl-Scalar-List-Utils-1.49-2.el8 | ||
CVE-2023-47038 | Twistlock CVE | Medium | perl-threads-shared-1.58-2.el8 | ||
CVE-2023-47038 | Twistlock CVE | Medium | perl-IO-Socket-IP-0.39-5.el8 | ||
CVE-2022-40896 | Twistlock CVE | Medium | python3.11-pip-22.3.1-5.el8 | ||
CVE-2019-13118 | Twistlock CVE | Low | libxslt-1.1.32-6.el8 | ||
CVE-2019-13117 | Twistlock CVE | Low | libxslt-1.1.32-6.el8 | ||
CVE-2024-0397 | Twistlock CVE | Low | python3.11-3.11.11-1.el8_10 | ||
CVE-2024-7592 | Twistlock CVE | Low | python3.11-3.11.11-1.el8_10 | ||
CVE-2023-5752 | Twistlock CVE | Low | pip-22.3.1 | ||
CVE-2023-0465 | Anchore CVE | Low | openssl-1:1.1.1k-14.el8_6 | ||
CVE-2022-27943 | Anchore CVE | Low | libgomp-8.5.0-22.el8_10 | ||
CVE-2018-19211 | Anchore CVE | Low | ncurses-6.1-10.20180224.el8 | ||
CVE-2023-0464 | Anchore CVE | Low | openssl-1:1.1.1k-14.el8_6 | ||
CVE-2022-40896 | Anchore CVE | Medium | python3.11-pip-wheel-22.3.1-5.el8 | ||
CVE-2024-41996 | Anchore CVE | Low | openssl-1:1.1.1k-14.el8_6 | ||
CVE-2018-19217 | Anchore CVE | Low | ncurses-6.1-10.20180224.el8 | ||
CVE-2020-19185 | Anchore CVE | Low | ncurses-6.1-10.20180224.el8 | ||
CVE-2019-13118 | Anchore CVE | Low | libxslt-1.1.32-6.el8 | ||
CVE-2020-19187 | Anchore CVE | Low | ncurses-6.1-10.20180224.el8 | ||
CVE-2019-14250 | Anchore CVE | Low | libgomp-8.5.0-22.el8_10 | ||
CVE-2020-19189 | Anchore CVE | Low | ncurses-6.1-10.20180224.el8 | ||
CVE-2024-0727 | Anchore CVE | Low | openssl-1:1.1.1k-14.el8_6 | ||
CVE-2023-50495 | Anchore CVE | Low | ncurses-6.1-10.20180224.el8 | ||
CVE-2020-19186 | Anchore CVE | Low | ncurses-6.1-10.20180224.el8 | ||
CVE-2023-45918 | Anchore CVE | Low | ncurses-6.1-10.20180224.el8 | ||
CVE-2019-13117 | Anchore CVE | Low | libxslt-1.1.32-6.el8 | ||
CVE-2024-7592 | Anchore CVE | Low | python3.11-3.11.11-1.el8_10 | ||
CVE-2024-7592 | Anchore CVE | Low | python3.11-libs-3.11.11-1.el8_10 | ||
CVE-2020-19188 | Anchore CVE | Low | ncurses-6.1-10.20180224.el8 | ||
CVE-2023-2650 | Anchore CVE | Medium | openssl-1:1.1.1k-14.el8_6 | ||
CVE-2024-4741 | Anchore CVE | Low | openssl-1:1.1.1k-14.el8_6 | ||
CVE-2023-0466 | Anchore CVE | Low | openssl-1:1.1.1k-14.el8_6 | ||
CVE-2018-20657 | Anchore CVE | Low | libgomp-8.5.0-22.el8_10 | ||
CVE-2024-2511 | Anchore CVE | Low | openssl-1:1.1.1k-14.el8_6 | ||
CVE-2019-17543 | Anchore CVE | Medium | lz4-1.8.3-3.el8_4 | ||
CVE-2021-39537 | Anchore CVE | Low | ncurses-6.1-10.20180224.el8 | ||
CVE-2022-40896 | Anchore CVE | Medium | python3.11-pip-22.3.1-5.el8 | ||
CVE-2020-19190 | Anchore CVE | Low | ncurses-6.1-10.20180224.el8 | ||
CCE-85987-6 | OSCAP Compliance | Medium |
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=enterprisedb/edb-postgres-advanced-16&tag=16.6.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.