Yaml AxisApplication · Jenkins
CVE-2020-2179
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 Yaml Axis Plugin 0.2.0 and earlier does not configure its YAML parser to prevent the instantiation of arbitrary types, resulting in a remote code execution vulnerability.
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 Yaml Axis Plugin versions 0.2.0 and earlier contains an unsafe YAML parser configuration that allows instantiation of arbitrary types, enabling remote code execution. This is a deserialization vulnerability where the parser does not restrict which classes can be instantiated during YAML parsing.
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
Yaml AxisApplication
<= 0.2.0CVSS 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 if Jenkins Yaml Axis plugin is installedLocate the plugin in the Jenkins plugins directory (typically $JENKINS_HOME/plugins/) or via Jenkins UI at Manage Jenkins > Manage Plugins > Installed tab, searching for 'Yaml Axis' or 'yaml-axis'Affected if The plugin is present in the plugins directory or listed in the Jenkins plugin management UI
-
Determine the installed plugin versionIf the plugin .jpi or .hpi file exists in $JENKINS_HOME/plugins/, examine the MANIFEST.MF file inside the plugin archive for the Implementation-Version attribute. Alternatively, view the version displayed in the Jenkins UI plugin details
-
Confirm the affected version rangeCompare your identified version against the known affected range: any version 0.2.0 or earlier. Version 0.3.0 and later are not affectedAffected if Your installed version is less than or equal to 0.2.0, indicating the vulnerable unsafe YAML parser configuration is present
If the Jenkins Yaml Axis Plugin version is 0.2.0 or earlier, your environment contains the unsafe YAML parser configuration and is affected by this CVE.
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 Yaml Axis Plugin to version 0.3.0 or later, which configures the YAML parser to prevent arbitrary type instantiation. If upgrading is not immediately possible, restrict plugin access to trusted users only.
Fix this in Yaml Axis
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-2179 — 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-2020-2179 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