CVE-2021-0279
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 · uneditedJuniper Networks Contrail Cloud (CC) releases prior to 13.6.0 have RabbitMQ service enabled by default with hardcoded credentials. The messaging services of RabbitMQ are used when coordinating operations and status information among Contrail services. An attacker with access to an administrative service for RabbitMQ (e.g. GUI), can use these hardcoded credentials to cause a Denial of Service (DoS) or have access to unspecified sensitive system information. This issue affects the Juniper Networks Contrail Cloud releases on versions prior to 13.6.0.
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 confidenceRabbitMQ service in Juniper Contrail Cloud prior to version 13.6.0 ships with hardcoded default credentials. Since RabbitMQ handles inter-service messaging for Contrail coordination, an attacker with access to the RabbitMQ administrative interface can leverage these credentials to cause denial of service or exfiltrate sensitive system information.
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< 13.6CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/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.
-
Confirm Juniper Contrail Cloud installationIdentify whether Juniper Contrail Cloud is deployed in your environment by checking for Contrail-related services, components, or documentation.Affected if Contrail Cloud is installed and the version is unknown or below 13.6.0
-
Determine Contrail Cloud versionLocate the installed Contrail Cloud version through package management, documentation, or command-line tools that report the installed software version.Affected if The installed version is any version prior to 13.6.0 (for example, 13.5.x or earlier)
-
Locate RabbitMQ configurationFind the RabbitMQ configuration files or deployment manifests used by Contrail Cloud. These typically define connection parameters, user credentials, and enabled plugins.Affected if RabbitMQ configuration files exist and contain hardcoded or default credentials rather than site-specific unique credentials
-
Inspect RabbitMQ credentialsExamine RabbitMQ configuration for username and password values. Compare these against known default credential patterns or vendor documentation for default values.Affected if The credentials appear to be factory defaults or are identical across multiple deployments rather than unique to your environment
-
Verify administrative interface exposureCheck RabbitMQ management plugin or administrative interface binding. Determine if it listens on external interfaces or is restricted to localhost or trusted networks.Affected if RabbitMQ administrative interface is accessible from untrusted networks or uses default credentials when accessed
Your environment is affected if you are running any version of Juniper Contrail Cloud prior to 13.6.0 and the RabbitMQ service still uses hardcoded default credentials or exposes its administrative interface to untrusted 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.
From vendor data13.6
Upgrade Contrail Cloud to version 13.6.0 or later to receive the patched RabbitMQ configuration with non-hardcoded credentials. Alternatively, if upgrading is not immediately feasible, change the default RabbitMQ credentials and restrict administrative interface access to trusted networks.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-0279 — 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-2021-0279 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