RundeckApplication · Jenkins
CVE-2019-16556
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 Rundeck Plugin 3.6.5 and earlier stores credentials unencrypted in its global configuration file and in job config.xml files on the Jenkins master where they can be viewed by users with Extended Read permission, or access to the master 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 Rundeck Plugin versions 3.6.5 and earlier stores credentials unencrypted in plaintext within global configuration files and job config.xml files on the Jenkins master. Users with Extended Read permission or filesystem access to the Jenkins master can view these stored credentials in cleartext.
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
RundeckApplication
<= 3.6.5CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/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.
-
Identify if Rundeck plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Rundeck' to confirm the plugin is present.Affected if The Rundeck plugin is installed and its version is 3.6.5 or earlier.
-
Determine the installed Rundeck plugin versionIn the Installed plugins tab, locate the Rundeck plugin and note the version number displayed in the 'Version' column.Affected if The version listed is 3.6.5 or lower.
-
Inspect global configuration files for stored credentialsLocate the Rundeck plugin global configuration file on the Jenkins master filesystem, typically found in the JENKINS_HOME directory under userContent or within the plugin's config.xml. Open the file and examine whether any credentials appear as plaintext rather than encrypted.Affected if Credentials are visible in cleartext within the global configuration file.
-
Examine job config.xml files for stored credentialsReview job configuration XML files in JENKINS_HOME/jobs/<jobname>/config.xml for any Rundeck-related build steps. Check whether any username, password, token, or API key values are stored as unencrypted plaintext strings.Affected if Rundeck-related credentials in job config.xml files are stored in plaintext.
You are affected if the Rundeck plugin version is 3.6.5 or earlier AND plaintext credentials are found in either global configuration files or job config.xml files.
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 Rundeck Plugin to version 3.6.6 or later to resolve the storage vulnerability, and rotate all credentials that were stored using the affected plugin versions as a precautionary measure.
Fix this in Rundeck
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-16556 — 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-2019-16556 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