Rabbitmq Docker ImageApplication · Docker
CVE-2020-35196
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe official rabbitmq docker images before 3.7.13-beta.1-management-alpine (Alpine specific) contain a blank password for a root user. System using the rabbitmq docker container deployed by affected versions of the docker image may allow a remote attacker to achieve root access with a blank password.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe official RabbitMQ Docker Alpine images before version 3.7.13-beta.1-management-alpine ship with a root user that has a blank password. This creates a trivial authentication bypass where remote attackers can connect to the RabbitMQ management interface or SSH into the container using the root account with no password, achieving full root access to the containerized environment.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Rabbitmq Docker ImageApplication
<= 3.7.12CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the installed RabbitMQ Docker image versionRun 'docker images' and check the TAG column for the RabbitMQ image, or run 'docker inspect <container_id>' and look at the Image tagAffected if The image tag shows version 3.7.12 or lower, or contains 'alpine' in the tag name with no version visible that is higher than 3.7.12
-
Confirm the image is Alpine-basedRun 'docker inspect <image_id>' and look for 'Alpine' in the OS/Architecture fields, or check if the tag contains 'alpine'Affected if The image is based on Alpine Linux (tag contains 'alpine') and the version is 3.7.12 or earlier
-
Check if the management interface port is exposedRun 'docker inspect <container_id>' and look for ExposedPorts in the config, or run 'docker ps' to see published portsAffected if Port 15672 (management UI) or 5672 (AMQP) is published to the host or accessible remotely
-
Verify root user authentication configurationCheck the Docker image or container for /etc/passwd entries and look for root user configuration. Attempt to access the management interface at port 15672 using default guest:guest credentials, or check if no password is required for rootAffected if The root user has no password set, or default guest credentials work without modification, allowing unauthenticated access
-
Check for SSH access enabled in the containerInspect the container for running SSH daemon (port 22) or check image Dockerfile/Entrypoint for SSH configurationAffected if SSH is enabled and accessible with root user and no password required
You are affected if you are running a RabbitMQ Docker Alpine image version 3.7.12 or lower with exposed management interface or SSH access, where the root user has a blank password allowing unauthenticated remote access.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedImmediately upgrade to a patched RabbitMQ Docker image version 3.7.13-beta.1-management-alpine or later, and enforce strong authentication credentials for all users, especially the root user.
RabbitMQ Docker Image >= 3.7.13 (or 3.7.13-beta.1-management-alpine for Alpine variants)
- 1. Stop any running containers using the affected RabbitMQ Docker image
- 2. Pull the fixed RabbitMQ Docker image version 3.7.13 or later (or 3.7.13-beta.1-management-alpine or newer for Alpine variants)
- 3. Update your docker-compose.yml or Kubernetes manifests to reference the new image version
- 4. Ensure any persistent volumes with the old image are properly backed up before recreation
- 5. Start the new container with the updated image
- 6. Verify that the root user now has a proper password configured or that authentication is properly enforced
- 7. Test RabbitMQ functionality to ensure the upgrade did not break existing applications
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Rabbitmq Docker Image
Scoped from the published advisory
- Consultation3.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,592.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-35196 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-35196 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data