dbcve.org
RepoApplication · Jenkins

CVE-2022-43415

HIGH · 7.5 CVSS v3.1 Published 2022-10-19
Fix available
A fix is available. Upgrade to 1.16.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 REPO Plugin 1.15.0 and earlier does not configure its XML parser to prevent XML external entity (XXE) attacks.

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

The Jenkins REPO Plugin versions 1.15.0 and earlier contains a vulnerability where its XML parser is not configured to prevent XML External Entity (XXE) attacks. This allows attackers to inject malicious external entity references into XML input processed by the plugin, potentially leading to disclosure of internal files, SSRF, or denial of service.

MitigationUpgrade the Jenkins REPO Plugin to version 1.15.1 or later, which configures the XML parser to disable external entity processing.

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
RepoApplication
Affected:< 1.16.0

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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. Verify REPO Plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab, or inspect the plugin directory (typically $JENKINS_HOME/plugins/repo/) for the repo plugin files
    Affected if The REPO Plugin is not present in the plugin list or directory
  2. Identify installed REPO Plugin version
    In Jenkins UI, go to Manage Jenkins > Manage Plugins > Installed and locate the REPO Plugin to view its version number. Alternatively, check the plugin's manifest file (META-INF/MANIFEST.MF) inside the plugin archive
    Affected if Unable to determine version or version displays as 1.15.0 or earlier
  3. Compare version against affected range
    Compare the installed version number to the affected range: versions 1.15.0 and earlier are vulnerable. Version 1.16.0 and later contain the fix
    Affected if Installed version is 1.15.0 or earlier, or any version less than 1.16.0
  4. Check for XML import usage
    Review Jenkins job configurations and pipeline scripts to determine if the REPO Plugin is used to fetch, parse, or process XML files or repositories containing XML content
    Affected if The plugin is actively used to process XML data from external sources

The environment is affected if the Jenkins REPO Plugin is installed with version 1.15.0 or earlier (less than 1.16.0) and the plugin is used to process XML data.

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 1.16.0 or later
Fixed in 1.16.0
Interim mitigation

Upgrade the Jenkins REPO Plugin to version 1.15.1 or later, which configures the XML parser to disable external entity processing.

Recommended fix High confidence

Jenkins REPO Plugin 1.16.0

  1. 1. Identify the current version of the Jenkins REPO Plugin installed by navigating to Manage Jenkins > Manage Plugins > Installed tab
  2. 2. Locate the REPO Plugin in the list and note its current version
  3. 3. If the version is 1.15.0 or earlier, navigate to the Available tab or check for updates
  4. 4. Select the REPO Plugin and click 'Install' or 'Update' to upgrade to version 1.16.0 or later
  5. 5. After installation completes, restart Jenkins (or click 'Restart Now' if prompted) to apply the changes

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

Fix this in Repo Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-43415 — 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-43415 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