Configuration As CodeApplication · Jenkins
CVE-2019-10362
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.24 and earlier did not escape values resulting in variable interpolation during configuration import when exporting, allowing attackers with permission to change Jenkins system configuration to obtain the values of environment variables.
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.24 and earlier fail to properly escape values during configuration export, allowing variable interpolation to occur. Attackers with permission to modify Jenkins system configuration can exploit this to read sensitive environment variable values through the export function.
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.24CVSS 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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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.
-
Check if Configuration as Code plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab, or check the plugins directory for jenkins/config-as-code/config-as-code.jpiAffected if The plugin is not installed or has been removed entirely from the Jenkins instance
-
Determine the installed version of Configuration as Code pluginIn Jenkins UI, go to Manage Jenkins > Manage Plugins > Installed tab and locate 'Configuration as Code' in the list to view its version numberAffected if The installed version is 1.24 or earlier (any version <= 1.24)
-
Check user permissions for system configuration accessNavigate to Manage Jenkins > Manage Users or check Matrix-based security settings to see which users or groups have the 'Administer' permission or specifically permission to configure the systemAffected if Users other than administrators have permission to modify system configuration or if any untrusted users have elevated privileges
-
Verify if configuration export is accessibleAttempt to access the export function at <jenkins_url>/configuration-as-code/export or check via Manage Jenkins > Configuration as Code > Export Configuration (if the plugin UI is accessible)Affected if The export functionality is available and accessible to users with configuration permissions
You are affected if the Configuration as Code plugin version is 1.24 or earlier AND untrusted users have permission to modify Jenkins system configuration and can access the export function.
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 Jenkins Configuration as Code Plugin to version 1.25 or later which contains the fix for proper value escaping. Limit who has permission to change system configuration in the meantime.
Fix this in Configuration As Code
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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 $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10362 — 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-10362 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