Scan Another

CVE Scan for bitnamilegacy/rabbitmq:4.0.5

Docker image vulnerability scanner

134 Known Vulnerabilities in this Docker Image

1
Critical
34
High
36
Medium
61
Low
0
Info/ Unspecified/ Unknown
CVE IDSeverityPackageAffected VersionFixed VersionCVSS Score
CVE-2026-45447criticalopenssl<3.0.20-1~deb12u23.0.20-1~deb12u29.8

Issue summary: A specially crafted PKCS#7 or S/MIME signed message could trigger a use-after-free during PKCS#7 signature verification. Impact summary: A use-after-free may result in process crashes, heap corruption, or potentially remote code execution. When processing a PKCS#7 or S/MIME signed message, if the SignedData digestAlgorithms field is present as an empty ASN.1 SET, OpenSSL may incorrectly free a caller-owned BIO during PKCS7_verify(). A subsequent use of the BIO by the calling application results in a use-after-free condition. In the common case this occurs when the application later calls BIO_free() on the BIO originally passed to PKCS7_verify(). Depending on allocator behavior and application-specific BIO usage patterns, this may result in a crash or other memory corruption. In some application contexts this may potentially be exploitable for remote code execution. Applications that process PKCS#7 or S/MIME signed messages using OpenSSL PKCS#7 APIs may be affected. Applications using the CMS APIs for this processing are not affected. The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.

Relevance:

Since the provided CVE description is missing, a definitive assessment cannot be made; however, if the vulnerability involves remote code execution or unauthorized access to the RabbitMQ management interface, it would be highly relevant for standard deployments. It would become critical in scenarios where the Docker container is exposed to the public internet or an untrusted network without robust authentication and firewall rules. To ensure security, you should verify if your configuration enables the specific feature or port targeted by this CVE. (Note: Relevance analysis is automatically generated and may require verification.)

Package URL(s):
  • pkg:deb/debian/openssl@3.0.15-1~deb12u1?os_distro=bookworm&os_name=debian&os_version=12
CVE-2011-10007highlibfile-find-rule-perl<0.34-4~deb12u10.34-4~deb12u18.8
CVE-2026-0861highglibc<2.36-9+deb12u142.36-9+deb12u148.4
CVE-2025-6297highdpkg<1.21.231.21.238.2
CVE-2026-42013highgnutls28<3.7.9-2+deb12u73.7.9-2+deb12u78.2
CVE-2026-5260highgnutls28<3.7.9-2+deb12u73.7.9-2+deb12u78.2
CVE-2023-31484highperl<5.36.0-7+deb12u35.36.0-7+deb12u38.1
CVE-2026-28387highopenssl<3.0.19-1~deb12u23.0.19-1~deb12u28.1
CVE-2026-7383highopenssl<3.0.20-1~deb12u23.0.20-1~deb12u28.1
CVE-2025-4802highglibc<2.36-9+deb12u112.36-9+deb12u117.8

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.

Connect Github