CVE-2021-0212
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 · uneditedAn Information Exposure vulnerability in Juniper Networks Contrail Networking allows a locally authenticated attacker able to read files to retrieve administrator credentials stored in plaintext thereby elevating their privileges over the system. This issue affects: Juniper Networks Contrail Networking versions prior to 1911.31.
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 confidenceA locally authenticated attacker with file read access can obtain plaintext administrator credentials stored on the system, allowing privilege escalation to administrator level. The vulnerability stems from insecure storage of credentials in Contrail Networking versions prior to 1911.31.
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< 1911.31CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N
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 Contrail Networking installationRun 'contrail-version' or check for contrail packages installed via package manager (rpm -qa | grep contrail or dpkg -l | grep contrail)Affected if Contrail Networking is installed and version is below 1911.31
-
Determine Contrail versionExecute 'contrail-version' or inspect /etc/contrail/version file if present, then compare against the affected range of versions prior to 1911.31Affected if Installed version is any release prior to 1911.31 (e.g., 1910.x, 1911.0-1911.30, or earlier)
-
Locate credential storage filesSearch for configuration or database files that store administrator credentials, typically under /etc/contrail or /var/lib/contrail directoriesAffected if Credential files exist in plaintext form without encryption protection
-
Inspect file permissions on credential storageUse 'ls -la' on identified credential storage directories and files to verify if non-privileged users can read themAffected if Files containing administrator credentials are readable by users other than root or the contrail service account
-
Check for plaintext credentialsExamine identified credential files using 'cat' or a text viewer to look for unencrypted username and password pairsAffected if Plaintext administrator usernames and passwords are present in configuration or database files
User is affected if Contrail Networking version is below 1911.31 AND plaintext administrator credentials are stored in files accessible to local users with file read 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 data1911.31
Upgrade to Contrail Networking version 1911.31 or later which addresses the plaintext credential storage issue. If immediate upgrade is not possible, restrict local file access permissions and audit user accounts with filesystem access.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-0212 — 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-0212 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