Configuration As CodeApplication · Jenkins
CVE-2019-10345
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 Configuration as Code Plugin 1.20 and earlier did not treat the proxy password as a secret to be masked when logging or encrypted for export.
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 confidenceJenkins Configuration as Code Plugin versions 1.20 and earlier failed to treat proxy passwords as sensitive secrets. The password was logged in plaintext and was not encrypted when configurations were exported, allowing unauthorized access to the proxy credential through log files or exported configuration data.
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
Configuration As CodeApplication
< 1.20CVSS 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.
-
Identify JCasC plugin versionIn Jenkins, go to Manage Jenkins > Manage Plugins > Installed tab and locate 'Configuration as Code' plugin to see its version number, or use the Jenkins CLI: jenkins-cli.jar who-am-i with the plugin information endpoint.Affected if The installed version is 1.20 or earlier (any version listed as < 1.21)
-
Determine if proxy configuration is in useReview your JCasC YAML configuration file for any 'proxy' or 'httpProxy' sections, or check the Jenkins main configuration for proxy settings that JCasC might be managing.Affected if Proxy credentials (username and password) are configured in the JCasC-managed configuration.
-
Inspect Jenkins logs for plaintext passwordsExamine Jenkins log files (typically in $JENKINS_HOME/logs/ or the main jenkins.log) for any entries containing the configured proxy username or recognizable patterns of proxy password plaintext.Affected if Log files contain plaintext proxy password strings matching your configured proxy credential.
-
Review exported JCasC configurationIf you have previously exported your JCasC configuration (via the /configuration-as-code/export endpoint or via export commands), open those exported YAML files and check if proxy password values appear as plain text rather than masked or encrypted.Affected if Exported configuration files contain unmasked proxy passwords in plaintext.
You are affected if the JCasC plugin version is 1.20 or earlier and you have proxy credentials configured, with plaintext passwords appearing in logs or exported configurations.
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 data1.20
Upgrade Jenkins Configuration as Code Plugin to version 1.21 or later where proxy passwords are properly masked in logs and encrypted during export.
Fix this in Configuration As Code
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10345 — 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-10345 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