NomadApplication · Jenkins
CVE-2021-21681
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 · uneditedJenkins Nomad Plugin 0.7.4 and earlier stores Docker passwords unencrypted in the global config.xml file on the Jenkins controller where they can be viewed by users with access to the Jenkins controller file system.
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 Jenkins Nomad Plugin version 0.7.4 and earlier stores Docker passwords in plaintext within the global config.xml file on the Jenkins controller. Users with file system access to the Jenkins controller can view these unencrypted passwords, resulting in credential disclosure.
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
NomadApplication
<= 0.7.4CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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.
-
Verify Jenkins Nomad Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed and look for 'Nomad' in the list, or use the Jenkins CLI: java -jar jenkins-cli.jar list-plugins 2>/dev/null | grep -i nomadAffected if The Nomad plugin is installed and the version is 0.7.4 or earlier
-
Check Nomad plugin versionIn Jenkins UI, go to Manage Jenkins > Manage Plugins > Installed and locate the Nomad plugin to view its version numberAffected if Version is 0.7.4 or earlier (or version cannot be determined but plugin is present)
-
Confirm Docker password is configured in NomadNavigate to Manage Jenkins > Configure System > Nomad Cloud Provisioner and check if a Docker password field is populatedAffected if A Docker password is configured in the Nomad plugin settings (this is required for the flaw to apply)
-
Inspect global config.xml for plaintext passwordLocate the Jenkins global configuration file (config.xml) and search within it for the Nomad plugin configuration section. Look for a <dockerPassword> or similar field and check whether its value appears as plaintext (readable text) rather than an encrypted hash or referenceAffected if The password value in config.xml appears as plaintext readable text instead of being encrypted or masked
The environment is affected if the Nomad plugin version is 0.7.4 or earlier AND a Docker password is configured AND that password is stored in plaintext within the config.xml file.
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 dataUpgrade the Jenkins Nomad Plugin to a version that encrypts stored passwords. Additionally, restrict filesystem access to the Jenkins controller to only authorized administrators.
Fix this in Nomad
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-21681 — 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-21681 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