dbcve.org
ViolationsApplication · Jenkins

CVE-2022-45386

MEDIUM · 5.5 CVSS v3.1 Published 2022-11-15
Fix available
A fix is available. Upgrade to after 0.7.11 or later.
See remediation →
58/100
Remediation priority · Elevated
No privileges

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 Violations Plugin 0.7.11 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 Violations Plugin versions 0.7.11 and earlier contains an XML External Entity (XXE) vulnerability due to its XML parser not being configured securely. An attacker who can provide a malicious XML file to be parsed by the plugin could cause the parser to load external entities, potentially leading to disclosure of sensitive information or server-side request forgery.

MitigationUpgrade Jenkins Violations Plugin to version 0.8.0 or later which configures the XML parser to prevent XXE attacks. If upgrading is not immediately possible, ensure that untrusted XML files are not processed by the plugin.

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
ViolationsApplication
Affected:<= 0.7.11

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 Violations plugin is installed
    In Jenkins, go to Manage Jenkins > Manage Plugins > Installed tab and search for 'Violations' in the list of installed plugins.
    Affected if The Violations plugin appears in the installed plugins list.
  2. Identify the installed Violations plugin version
    In the Installed plugins list, locate the Violations plugin and note the Version column. Alternatively, click on the plugin to view its details.
    Affected if The version is 0.7.11 or lower.
  3. Confirm the plugin is enabled
    In Manage Plugins > Installed, verify the Violations plugin is Enabled (the checkbox is ticked).
    Affected if The plugin is enabled and actively running.
  4. Check if XML files are being processed by the plugin
    Review Jenkins job configurations that use the Violations plugin. Look for build steps or post-build actions that import violation reports in XML format.
    Affected if Jobs are configured to parse XML files using the Violations plugin.
  5. Determine if untrusted XML input can reach the plugin
    Examine who can upload or trigger processing of XML files that the Violations plugin will parse. Check if external users or automated pipelines can supply these files without validation.
    Affected if Untrusted or external parties can submit XML files that the plugin will process.

You are affected if the Violations plugin version 0.7.11 or earlier is installed, enabled, and configured to parse XML files that could be supplied by untrusted sources.

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 0.7.11
Interim mitigation

Upgrade Jenkins Violations Plugin to version 0.8.0 or later which configures the XML parser to prevent XXE attacks. If upgrading is not immediately possible, ensure that untrusted XML files are not processed by the plugin.

Recommended fix Moderate confidence

Version 0.7.12 or later of the Jenkins Violations Plugin

  1. 1. Navigate to the Jenkins dashboard
  2. 2. Go to Manage Jenkins > Manage Plugins
  3. 3. Click on the 'Installed' tab
  4. 4. Find the 'Violations' plugin in the list
  5. 5. Check if an update is available for the Violations plugin
  6. 6. If an update is available, click 'Update' to upgrade to a version newer than 0.7.11
  7. 7. Restart Jenkins if required to complete the installation

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

Fix this in Violations Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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 locally
dbcve dependency scanner

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