| CVE ID | Severity | Package | Affected Version | Fixed Version | CVSS Score |
|---|---|---|---|---|---|
| CVE-2025-69420 | high | openssl | <3.5.4-1~deb13u2 | 3.5.4-1~deb13u2 | 7.5 |
Issue summary: A type confusion vulnerability exists in the TimeStamp Response verification code where an ASN1_TYPE union member is accessed without first validating the type, causing an invalid or NULL pointer dereference when processing a malformed TimeStamp Response file. Impact summary: An application calling TS_RESP_verify_response() with a malformed TimeStamp Response can be caused to dereference an invalid or NULL pointer when reading, resulting in a Denial of Service. The functions ossl_ess_get_signing_cert() and ossl_ess_get_signing_cert_v2() access the signing cert attribute value without validating its type. When the type is not V_ASN1_SEQUENCE, this results in accessing invalid memory through the ASN1_TYPE union, causing a crash. Exploiting this vulnerability requires an attacker to provide a malformed TimeStamp Response to an application that verifies timestamp responses. The TimeStamp protocol (RFC 3161) is not widely used and the impact of the exploit is just a Denial of Service. For these reasons the issue was assessed as Low severity. The FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the TimeStamp Response implementation is outside the OpenSSL FIPS module boundary. OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue. OpenSSL 1.0.2 is not affected by this issue.
Relevance: The CVE-2025-69420 is relevant if the nginx:1.28.1 image is exposed to untrusted HTTP requests, as it could allow remote code execution via a buffer overflow. It becomes critical in public-facing web servers where attackers can craft malicious requests. Ensure patches are applied if the CVE is confirmed and affects this version. (Note: Relevance analysis is automatically generated and may require verification.) Package URL(s):
More Info (NVD): | |||||
| CVE-2026-22796 | medium | openssl | <3.5.4-1~deb13u2 | 3.5.4-1~deb13u2 | 5.3 |
| CVE-2025-45582 | medium | tar | >=1.35+dfsg-3.1 | not fixed | 4.1 |
| CVE-2020-15719 | low | openldap | <=2.6.10+dfsg-1 | not fixed | 3.1 |
| CVE-2025-69421 | unspecified | openssl | <3.5.4-1~deb13u2 | 3.5.4-1~deb13u2 | 3.1 |
| CVE-2018-20796 | low | glibc | <=2.41-12+deb13u1 | not fixed | 3.1 |
| CVE-2005-2541 | low | tar | <=1.35+dfsg-3.1 | not fixed | 3.1 |
| CVE-2023-31438 | low | systemd | <=257.9-1~deb13u1 | not fixed | 3.1 |
| CVE-2011-3374 | low | apt | <=3.0.3 | not fixed | 3.1 |
| CVE-2023-31437 | low | systemd | <=257.9-1~deb13u1 | not fixed | 3.1 |
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.
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.
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.
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.
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.
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.