Coverage\/complexity Scatter PlotApplication · Jenkins
CVE-2022-28154
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 · uneditedJenkins Coverage/Complexity Scatter Plot Plugin 1.1.1 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 confidenceThe Jenkins Coverage/Complexity Scatter Plot Plugin versions 1.1.1 and earlier contains an XML External Entity (XXE) vulnerability due to its XML parser not being configured to prevent XXE attacks. An attacker with the ability to submit or influence XML input could exploit this to read local files, perform server-side request forgery (SSRF), or cause denial of service.
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
Coverage\/complexity Scatter PlotApplication
<= 1.1.1CVSS 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
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Verify plugin installationNavigate to Manage Jenkins > Manage Plugins > Installed tab, or inspect the plugin directory on the Jenkins controller (typically $JENKINS_HOME/plugins/). Look for the Coverage/Complexity Scatter Plot plugin.Affected if The plugin is present in the Jenkins installation
-
Check installed versionIn the plugin manager UI, check the version listed for Coverage/Complexity Scatter Plot. Alternatively, inspect the plugin's manifest file (MANIFEST.MF) located in the plugin's directory within $JENKINS_HOME/plugins/Affected if The installed version is 1.1.1 or earlier
-
Assess XML input exposureThe vulnerability requires the ability to submit or influence XML input processed by the plugin. Identify if the plugin is configured to accept or process XML files from user-controlled sources, such as XML-based coverage reports or configuration files.Affected if The plugin processes XML input that can be submitted or influenced by an attacker
The environment is affected if the Coverage/Complexity Scatter Plot Plugin version 1.1.1 or earlier is installed and is used to process XML input from sources that could be controlled or influenced by an attacker.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade to Jenkins Coverage/Complexity Scatter Plot Plugin version 1.1.2 or later, which includes proper XML parser configuration to prevent XXE attacks.
1.1.2 (or latest available version)
- Navigate to Jenkins Dashboard
- Go to Manage Jenkins
- Click on Manage Plugins
- Select the 'Installed' tab
- Find 'Coverage/Complexity Scatter Plot' plugin in the list
- If the plugin shows version 1.1.1 or earlier, click 'Update' to install the latest version
- Restart Jenkins if required to complete the update
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Coverage\/complexity Scatter Plot
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2022-28154 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-28154 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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