dbcve.org
Semantic VersioningApplication · Jenkins

CVE-2022-27201

MEDIUM · 6.5 CVSS v3.1 Published 2022-03-15
Fix available
A fix is available. Upgrade to after 1.13 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
Jenkins Semantic Versioning Plugin 1.13 and earlier does not restrict execution of an controller/agent message to agents, and implements no limitations about the file path that can be parsed, allowing attackers able to control agent processes to have Jenkins parse a crafted file that uses external entities for extraction of secrets from the Jenkins controller or server-side request forgery.

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 confidence

This is an XML External Entity (XXE) injection vulnerability in Jenkins Semantic Versioning Plugin where the controller accepts and parses messages from agents without proper restrictions. An attacker who compromises an agent can send a crafted message causing Jenkins to parse a malicious XML file containing external entity references, enabling extraction of secrets from the Jenkins controller filesystem or Server-Side Request Forgery (SSRF) attacks.

MitigationUpgrade to Jenkins Semantic Versioning Plugin version 1.14 or later which implements restrictions on agent-to-controller message execution and file path limitations.

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
Semantic VersioningApplication
Affected:<= 1.13

CVSS 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
None
Availability
None

CVSS:3.1/AV:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if Semantic Versioning Plugin is installed
    Go to Manage Jenkins > Manage Plugins > Installed and search for 'Semantic Versioning', or check the plugin directory $JENKINS_HOME/plugins for semantic-versioning-plugin folder and its manifest.json for the version
    Affected if Plugin is installed with version 1.13 or lower (version shown in manifest.json or plugin details)
  2. Verify the plugin version number
    Open the plugin's manifest file (META-INF/MANIFEST.MF or manifest.json) inside the plugin folder and locate the Implementation-Version attribute
    Affected if Implementation-Version is 1.13 or lower (the vulnerability is present in versions up to and including 1.13)
  3. Identify configured Jenkins agents
    Go to Manage Jenkins > Manage Nodes. Review the list of configured permanent agents and any configured clouds for ephemeral agents
    Affected if Any agents are configured and connected (the XXE attack requires a compromised agent to send crafted XML messages to the controller)
  4. Check for jobs using Semantic Versioning plugin
    Search job configurations for usage of the 'semantic-versioning' plugin or related build steps provided by this plugin
    Affected if Any jobs are configured to use the Semantic Versioning plugin (the plugin must be actively processing messages for the vulnerability to be triggerable)

You are affected if the Semantic Versioning Plugin version is 1.13 or lower AND you have configured agents or jobs that use the plugin, as the XXE flaw requires agent-to-controller message parsing to be triggerable.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 1.13
Interim mitigation

Upgrade to Jenkins Semantic Versioning Plugin version 1.14 or later which implements restrictions on agent-to-controller message execution and file path limitations.

Recommended fix Moderate confidence

Semantic Versioning Plugin 1.14 or later

  1. 1. Navigate to Jenkins dashboard
  2. 2. Go to Manage Jenkins > Manage Plugins
  3. 3. Click on the 'Installed' tab
  4. 4. Find the 'Semantic Versioning' plugin in the list
  5. 5. If the plugin shows version 1.13 or earlier, click 'Update' to upgrade to the latest available version
  6. 6. After update completes, restart Jenkins if required
  7. 7. Verify the upgraded version is 1.14 or later

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Semantic Versioning Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-27201 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-27201 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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