dbcve.org
Job Configuration HistoryApplication · Jenkins

CVE-2023-41933

HIGH · 8.8 CVSS v3.1 Published 2023-09-06
Fix available
A fix is available. Upgrade to after 1229.v3039470161a_d or later.
See remediation →
94/100
Remediation priority · Urgent
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 Job Configuration History Plugin 1227.v7a_79fc4dc01f 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 Job Configuration History Plugin versions 1227.v7a_79fc4dc01f and earlier contains an XML External Entity (XXE) vulnerability because its XML parser is not configured to prevent XXE attacks. An attacker could submit maliciously crafted XML content to the plugin, potentially allowing disclosure of sensitive files, SSRF attacks, or denial of service.

MitigationConfigure the XML parser to disable external entity processing by setting properties such as XMLConstants.ACCESS_EXTERNAL_DTD and XMLConstants.ACCESS_EXTERNAL_SCHEMA to empty strings, or use a secure XMLInputFactory with appropriate security features enabled.

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
Job Configuration HistoryApplication
Affected:<= 1229.v3039470161a_d

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
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 checks

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

  1. Verify Job Configuration History plugin is installed
    In Jenkins, go to Manage Jenkins > Manage Plugins > Installed tab and look for 'Job Configuration History' in the list of installed plugins, or use the Jenkins CLI: java -jar jenkins-cli.jar -s http://localhost:8080 list-plugins | grep -i 'job configuration history'
    Affected if The plugin is not installed, this CVE does not apply
  2. Check installed plugin version
    On the Installed plugins page, find the Job Configuration History plugin and note the Version column. Alternatively, check the plugin's manifest file located at $JENKINS_HOME/plugins/job-config-history/META-INF/MANIFEST.MF
    Affected if The version is 1229.v3039470161a_d or earlier (or 1227.v7a_79fc4dc01f or earlier based on the summary)
  3. Confirm plugin is actively processing job configurations
    Check if the plugin has created its history directories. Look for $JENKINS_HOME/jobs/*/builds/*/config.xml or similar configuration history folders, or verify the plugin is enabled in Manage Jenkins > Configure System > Job Configuration History
    Affected if The plugin is enabled and storing configuration history for jobs, meaning it processes XML configuration files
  4. Verify XML content handling
    The plugin stores job configuration history as XML files. Confirm that $JENKINS_HOME/jobs/<jobname>/config-history/ or similar history directories contain XML files created by the plugin
    Affected if XML configuration files are being stored by the plugin, indicating XML parsing is in use

If the Job Configuration History plugin is installed with version 1229.v3039470161a_d or earlier and is actively storing job configuration history (XML files), the environment is affected by this XXE vulnerability.

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 1229.v3039470161a_d
Interim mitigation

Configure the XML parser to disable external entity processing by setting properties such as XMLConstants.ACCESS_EXTERNAL_DTD and XMLConstants.ACCESS_EXTERNAL_SCHEMA to empty strings, or use a secure XMLInputFactory with appropriate security features enabled.

Recommended fix Moderate confidence

Upgrade to Job Configuration History plugin version 1231.vd6f8f8a_42e3 or later (refer to Jenkins security advisory for exact fixed version)

  1. 1. Identify the Jenkins instance running the Job Configuration History plugin.
  2. 2. Navigate to Manage Jenkins > Manage Plugins > Installed tab.
  3. 3. Locate the 'Job Configuration History' plugin and note the current version.
  4. 4. Check the Jenkins Security Advisory (jenkins.io/security/advisory/) for CVE-2023-41933 to identify the fixed version.
  5. 5. If the current version is <= 1227.v7a_79fc4dc01f, proceed with upgrade.
  6. 6. In the Plugin Manager, select the Job Configuration History plugin and click 'Update' or install the fixed version.
  7. 7. Restart Jenkins or click 'Apply' to complete the plugin update.
  8. 8. Verify the new plugin version is installed and Jenkins is operational.

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

Fix this in Job Configuration History Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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