Jenkins Cloudformation PluginPlugin / extension · Jenkins
CVE-2019-1003061
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 jenkins-cloudformation-plugin Plugin stores credentials unencrypted 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 jenkins-cloudformation-plugin stores credentials in plaintext within job config.xml files on the Jenkins master. Users with Extended Read permission or filesystem access to the master can view these unencrypted credentials directly.
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
Jenkins Cloudformation PluginPlugin / extension
all versionsCVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Verify jenkins-cloudformation-plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab, or run: ls $JENKINS_HOME/plugins/ | grep cloudformationAffected if The jenkins-cloudformation-plugin directory or JAR file exists in the plugins folder
-
Identify jobs using CloudFormation pluginSearch for job config.xml files containing 'jenkins-cloudformation-plugin' or cloudformation-related elements: find $JENKINS_HOME/jobs -name config.xml -exec grep -l -i cloudformation {} \;Affected if Any job config.xml files reference cloudformation-plugin configurations
-
Inspect job config.xml for plaintext credentialsExamine the content of identified config.xml files, looking for unencrypted password, secret, or credential fields stored in plaintext within cloudformation-related XML elementsAffected if config.xml contains plaintext passwords, API keys, or secrets in cleartext within cloudformation configuration sections
-
Check filesystem access to config.xml filesReview file permissions on job config.xml files: ls -la $JENKINS_HOME/jobs/*/config.xmlAffected if Filesystem permissions allow users other than the Jenkins service account to read config.xml files, exposing plaintext credentials
If the jenkins-cloudformation-plugin is installed AND job config.xml files contain plaintext credentials (passwords, secrets, or API keys in cleartext), the environment is affected by this vulnerability.
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 dataUpdate to a patched version of the jenkins-cloudformation-plugin, rotate all exposed credentials, and reconfigure credentials to use Jenkins' built-in encrypted credentials storage.
Fix this in Jenkins Cloudformation Plugin
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-1003061 — 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-1003061 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