CVE Scan for postgres:16
Docker image vulnerability scanner
102 Known Vulnerabilities in this Docker Image
| CVE ID | Severity | Package | Affected Version | Fixed Version | CVSS Score |
|---|---|---|---|---|---|
| CVE-2023-24538 | critical | pkg:golang/[email protected] | <1.19.8 | 1.19.8 | 9.8 |
Templates do not properly consider backticks (`) as Javascript string delimiters, and do not escape them as expected. Backticks are used, since ES6, for JS template literals. If a template contains a Go template action within a Javascript template literal, the contents of the action can be used to terminate the literal, injecting arbitrary Javascript code into the Go template. As ES6 template literals are rather complex, and themselves can do string interpolation, the decision was made to simply disallow Go template actions from being used inside of them (e.g. "var a = {{.}}"), since there is no obviously safe way to allow this behavior. This takes the same approach as github.com/google/safehtml. With fix, Template.Parse returns an Error when it encounters templates like this, with an ErrorCode of value 12. This ErrorCode is currently unexported, but will be exported in the release of Go 1.21. Users who rely on the previous behavior can re-enable it using the GODEBUG flag jstmpllitinterp=1, with the caveat that backticks will now be escaped. This should be used with caution. Package URL(s):
More Info (NVD): | |||||
| CVE-2023-24540 | critical | pkg:golang/[email protected] | <1.19.9 | 1.19.9 | 9.8 |
| CVE-2024-24790 | critical | pkg:golang/[email protected] | <1.21.11 | 1.21.11 | 9.8 |
| CVE-2025-22871 | critical | pkg:golang/[email protected] | <1.23.8 | 1.23.8 | 9.1 |
| CVE-2022-49043 | high | libxml2 | >=2.9.14+dfsg-1.3~deb12u1 | not fixed | 8.1 |
| CVE-2022-30580 | high | pkg:golang/[email protected] | >=1.18.0-0,<1.18.3 | 1.18.3 | 7.8 |
| CVE-2023-29403 | high | pkg:golang/[email protected] | <1.19.10 | 1.19.10 | 7.8 |
| CVE-2024-56171 | high | libxml2 | >=2.9.14+dfsg-1.3~deb12u1 | not fixed | 7.8 |
| CVE-2025-24928 | high | libxml2 | >=2.9.14+dfsg-1.3~deb12u1 | not fixed | 7.8 |
| CVE-2022-27664 | high | pkg:golang/[email protected] | <1.18.6 | 1.18.6 | 7.5 |
Severity Levels
Exploitation could lead to severe consequences, such as system compromise or data loss. Requires immediate attention.
Vulnerability could be exploited relatively easily and lead to significant impact. Requires prompt attention.
Exploitation is possible but might require specific conditions. Impact is moderate. Should be addressed in a timely manner.
Exploitation is difficult or impact is minimal. Address when convenient or as part of regular maintenance.
Severity is not determined, informational, or negligible. Review based on context.
Sliplane is a simple container hosting solution. It enables you to deploy your containers in the cloud within minutes and scale up as you grow.
About the CVE Scanner
What is a CVE?
CVE stands for Common Vulnerabilities and Exposures. It is a standardized identifier for known security vulnerabilities, allowing developers and organizations to track and address potential risks effectively. For more information, visit cve.mitre.org.
About the CVE Scanner
The CVE Scanner is a powerful tool that helps you identify known vulnerabilities in your Docker images. By scanning your images against a comprehensive database of Common Vulnerabilities and Exposures (CVEs), you can ensure that your applications are secure and up-to-date. For more details, checkout the NIST CVE Database.
How the CVE Scanner Works
The CVE Scanner analyzes your Docker images against a comprehensive database of known vulnerabilities. It uses Docker Scout under the hood to provide detailed insights into affected packages, severity levels, and available fixes, empowering you to take immediate action.
Why CVE Scanning is Essential for Your Docker Images
With the rise of supply chain attacks, ensuring the security of your applications has become more critical than ever. CVE scanning plays a vital role in identifying vulnerabilities that could be exploited by attackers, especially those introduced through dependencies and third-party components. Regularly scanning and securing your Docker images is essential to protect your applications from these evolving threats.
Benefits of CVE Scanning
- Enhanced Security: Detect and mitigate vulnerabilities before they are exploited.
- Compliance: Meet industry standards and regulatory requirements for secure software.
- Proactive Maintenance: Stay ahead of potential threats by addressing vulnerabilities early.
The Importance of Patching Docker Images
Patching your Docker images is a critical step in maintaining the security and stability of your applications. By regularly updating your images to include the latest security patches, you can address known vulnerabilities and reduce the risk of exploitation. This proactive approach ensures that your applications remain resilient against emerging threats and helps maintain compliance with security best practices.
Sliplane is not associated with Docker Inc. or any of its products. Prices do not include VAT.