CVE Scan for balabit/syslog-ng:nightly
Docker image vulnerability scanner
47 Known Vulnerabilities in this Docker Image
| CVE ID | Severity | Package | Affected Version | Fixed Version | CVSS Score |
|---|---|---|---|---|---|
| CVE-2025-66471 | high | pkg:pypi/urllib3@1.26.20 | >=1.0,<2.6.0 | 2.6.0 | 8.9 |
Impacturllib3's streaming API is designed for the efficient handling of large HTTP responses by reading the content in chunks, rather than loading the entire response body into memory at once. When streaming a compressed response, urllib3 can perform decoding or decompression based on the HTTP The decompression logic could cause urllib3 to fully decode a small amount of highly compressed data in a single operation. This can result in excessive resource consumption (high CPU usage and massive memory allocation for the decompressed data; CWE-409) on the client side, even if the application only requested a small chunk of data. Affected usagesApplications and libraries using urllib3 version 2.5.0 and earlier to stream large compressed responses or content from untrusted sources.
RemediationUpgrade to at least urllib3 v2.6.0 in which the library avoids decompressing data that exceeds the requested amount. If your environment contains a package facilitating the Brotli encoding, upgrade to at least Brotli 1.2.0 or brotlicffi 1.2.0.0 too. These versions are enforced by the CreditsThe issue was reported by @Cycloctane. Supplemental information was provided by @stamparm during a security audit performed by 7ASecurity and facilitated by OSTIF. Relevance: The relevance of CVE-2025-66471 depends on its nature; if it involves a critical vulnerability in syslog-ng or its dependencies, it could be highly relevant for the Docker image `balabit/syslog-ng:nightly`. It might become critical in scenarios where attackers exploit the vulnerability to compromise log integrity or escalate privileges, especially in production environments handling sensitive data. Always verify the CVE details and apply patches or updates if necessary. (Note: Relevance analysis is automatically generated and may require verification.) Package URL(s):
More Info (NVD): | |||||
| CVE-2025-66418 | high | pkg:pypi/urllib3@1.26.20 | >=1.24,<2.6.0 | 2.6.0 | 8.9 |
| CVE-2025-47287 | high | pkg:pypi/tornado@6.4.2 | <6.5 | 6.5.0 | 7.5 |
| CVE-2025-50181 | medium | pkg:pypi/urllib3@1.26.20 | <2.5.0 | 2.5.0 | 5.3 |
| CVE-2025-45582 | medium | tar | >=1.35+dfsg-3.1 | not fixed | 4.1 |
| CVE-2024-26464 | unspecified | net-snmp | >=5.9.4+dfsg-1 | not fixed | 3.1 |
| CVE-2024-26461 | low | krb5 | >=1.21.3-5 | not fixed | 3.1 |
| CVE-2021-45346 | low | sqlite3 | >=3.46.1-7 | not fixed | 3.1 |
| CVE-2024-2236 | low | libgcrypt20 | >=1.11.0-7 | not fixed | 3.1 |
| CVE-2017-14159 | low | openldap | >=2.6.10+dfsg-1 | not fixed | 3.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 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.