dbcve.org
Compuware Common ConfigurationApplication · Jenkins

CVE-2022-41226

CRITICAL · 9.8 CVSS v3.1 Published 2022-09-21
Fix available
A fix is available. Upgrade to 1.0.15 or later.
See remediation →
100/100
Remediation priority · Urgent
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 Compuware Common Configuration Plugin 1.0.14 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 Compuware Common Configuration Plugin versions 1.0.14 and earlier fails to secure its XML parser against XML External Entity (XXE) attacks. An attacker can submit specially crafted XML content containing malicious external entity references, potentially allowing disclosure of internal files, denial of service, or server-side request forgery (SSRF) attacks against the Jenkins server.

MitigationUpdate the Compuware Common Configuration Plugin to version 1.0.15 or later which properly configures the XML parser to disable external entity processing. If an update is unavailable, disable the plugin until a patch is released.

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
Compuware Common ConfigurationApplication
Affected:< 1.0.15

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 Compuware Common Configuration Plugin is installed
    In Jenkins, go to Manage Jenkins > Manage Plugins > Installed and search for 'Compuware Common Configuration' in the list of installed plugins.
    Affected if The plugin does not appear in the installed plugins list, then this CVE does not apply.
  2. Check the installed plugin version
    In the installed plugins list, locate the Compuware Common Configuration Plugin and note the Version column entry.
    Affected if The version is blank or cannot be determined from the UI, check the plugin manifest file directly in the Jenkins plugins directory.
  3. Compare version against vulnerable range
    Compare the installed version number to the affected range: versions 1.0.14 and earlier are vulnerable. Version 1.0.15 and later are fixed.
    Affected if The installed version is 1.0.14 or earlier, indicating the plugin has not been updated to address the XXE vulnerability.
  4. Verify XML parser security configuration (optional)
    Inspect the plugin configuration files or source code for XML parser setup. The vulnerable plugin will have XML parsing code that does not disable external entity processing (look for parser features preventing DOCTYPE declarations or external entity resolution).
    Affected if The XML parser is configured without disabling external entity processing, the plugin is vulnerable regardless of version.

The environment is affected if the Compuware Common Configuration Plugin is installed with version 1.0.14 or earlier, as these versions contain an insecure XML parser vulnerable to XXE attacks.

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.0.15 or later
Fixed in 1.0.15
Interim mitigation

Update the Compuware Common Configuration Plugin to version 1.0.15 or later which properly configures the XML parser to disable external entity processing. If an update is unavailable, disable the plugin until a patch is released.

Recommended fix High confidence

Compuware Common Configuration plugin version 1.0.15

  1. Log in to Jenkins as an administrator
  2. Navigate to 'Manage Jenkins' > 'Manage Plugins'
  3. Go to the 'Updates' tab
  4. Locate 'Compuware Common Configuration' plugin in the list
  5. Select the plugin and click 'Download now and install after restart'
  6. Wait for the plugin to download and install
  7. Restart Jenkins to complete the installation
  8. Verify the plugin shows version 1.0.15 or later under 'Manage Plugins' > 'Installed'

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

Fix this in Compuware Common Configuration Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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