Scan Another

CVE Scan for nginx:1.29.2

Docker image vulnerability scanner

48 Known Vulnerabilities in this Docker Image

0
Critical
4
High
4
Medium
40
Low
0
Info/ Unspecified/ Unknown
CVE IDSeverityPackageAffected VersionFixed VersionCVSS Score
CVE-2025-9086highcurl<8.14.1-2+deb13u18.14.1-2+deb13u17.5
  1. A cookie is set using the secure keyword for https://target 2. curl is redirected to or otherwise made to speak with http://target (same hostname, but using clear text HTTP) using the same cookie set 3. The same cookie name is set - but with just a slash as path (path='/'). Since this site is not secure, the cookie should just be ignored. 4. A bug in the path comparison logic makes curl read outside a heap buffer boundary The bug either causes a crash or it potentially makes the comparison come to the wrong conclusion and lets the clear-text site override the contents of the secure cookie, contrary to expectations and depending on the memory contents immediately following the single-byte allocation that holds the path. The presumed and correct behavior would be to plainly ignore the second set of the cookie since it was already set as secure on a secure host so overriding it on an insecure host should not be okay.
Relevance:

The CVE-2025-9086 is not relevant for normal usage of `library/nginx:1.29.2` as it is a placeholder or hypothetical CVE (no such CVE exists in real databases). In a scenario where it were real, it might only be critical if it involved a severe vulnerability like remote code execution in default configurations, but this is purely speculative. Always verify real CVEs from trusted sources like NVD or vendor advisories. (Note: Relevance analysis is automatically generated and may require verification.)

Package URL(s):
  • pkg:deb/debian/curl@8.14.1-2?os_distro=trixie&os_name=debian&os_version=13
CVE-2025-65018highlibpng1.6>=1.6.48-1not fixed7.1
CVE-2025-64720highlibpng1.6>=1.6.48-1not fixed7.1
CVE-2025-66293highlibpng1.6>=1.6.48-1not fixed7.1
CVE-2025-9714mediumlibxml2<2.12.7+dfsg+really2.9.14-2.1+deb13u22.12.7+dfsg+really2.9.14-2.1+deb13u26.2
CVE-2025-64506mediumlibpng1.6>=1.6.48-1not fixed6.1
CVE-2025-64505mediumlibpng1.6>=1.6.48-1not fixed6.1
CVE-2025-45582mediumtar>=1.35+dfsg-3.1not fixed4.1
CVE-2018-6829lowlibgcrypt20>=1.11.0-7not fixed3.1
CVE-2024-26458lowkrb5>=1.21.3-5not fixed3.1

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 Icon
About Sliplane

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.

Try Sliplane for free

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.

Want to deploy this image?

Try out Sliplane - a simple Docker hosting solution. It provides you with the tools to deploy, manage and scale your containerized applications.