RadargunApplication · Jenkins
CVE-2020-2123
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 RadarGun Plugin 1.7 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 · moderate confidenceThe Jenkins RadarGun Plugin versions 1.7 and earlier uses a YAML parser that is not configured to restrict type instantiation, allowing attackers to supply malicious YAML payloads that instantiate arbitrary classes and achieve remote code execution.
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
RadargunApplication
<= 1.7CVSS 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 RadarGun plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, or inspect $JENKINS_HOME/plugins/ for radargun directoryAffected if RadarGun plugin exists in the Jenkins plugins directory
-
Determine installed RadarGun versionCheck the plugin's manifest file (META-INF/MANIFEST.MF) inside the radargun plugin directory, or view the version listed in the Jenkins plugin manager UIAffected if Version listed is 1.7 or lower
-
Identify YAML-based RadarGun configuration usageReview Jenkins job configurations that use RadarGun build steps, particularly any that load YAML-based configuration files or use YAML for plugin settingsAffected if Jobs or pipeline scripts invoke RadarGun with YAML-defined profiles or configurations
-
Check for custom YAML SafeConstructor configurationInspect RadarGun plugin configuration files or any custom Jenkins scripts that initialize the YAML parser, looking for explicit SafeConstructor or safe type restriction settingsAffected if No safe type restrictions are configured for the YAML parser (the plugin uses default unsafe deserialization)
A user is affected if RadarGun plugin version 1.7 or lower is installed AND the plugin is used to parse YAML configurations without safe type restrictions applied.
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 RadarGun Plugin to a version later than 1.7 where the YAML parser is properly configured with safe type restrictions, or manually configure the YAML parser to use a SafeConstructor that blocks dangerous type instantiations.
Fix this in Radargun
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-2123 — 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-2123 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