-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Security Vulnerabilities in PostgreSQL Image: Request for Guidance #138
Comments
@SanduDS, we are transitioning away from the official Postgres image and are now in the process of approving a new build process that includes Software Bill of Materials (SBOMs) and signatures. Currently, the images are published in the "postgresql-testing" repository. Could you please evaluate them? For example, you can check Thank you! |
@gbartolini Are you confident enough to recommend images published under postgresql-testing to be used in production deployments? |
Closing this, the new images are better and already in production. Please if there's any further issues, open a new issue |
@sxd |
@cthtrifork yes, but if you share a screenshot I can't tell you what was the CVE in question, and you should point thae CVE not a messages saying "vulnerabilities", also, keep in mind that we cannot fix CVEs in the OS. |
Ah the information of your referred changes is available here: Looks good! |
Issue Description
We are using the PostgreSQL image (17) based on Debian OS (Bookworm) with CloudNativePG in our Kubernetes cluster. While scanning the image for vulnerabilities, we identified several critical issues. We need guidance from the CNPG community to address these vulnerabilities in the image version used by CNPG.
Critical Vulnerabilities Identified
CVE-2023-45853:
zipOpenNewFileInZip4_6
leads to a heap-based buffer overflow.will_not_fix
CVE-2023-24538:
html/template
)CVE-2023-24540:
html/template
)CVE-2024-24790:
net/netip
)Is
methods for IPv4-mapped IPv6 addresses could bypass IP-based restrictions.Impact on Cluster Security
While PostgreSQL itself is not directly impacted, associated vulnerabilities in the image pose a risk:
html/template
.net/netip
issues.Request for Guidance
Environment Details
We look forward to the community's insights and recommendations. Thank you!
The text was updated successfully, but these errors were encountered: