CppcheckApplication · Jenkins
CVE-2023-28678
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 Cppcheck Plugin 1.26 and earlier does not escape file names from Cppcheck report files before showing them on the Jenkins UI, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to control report file contents.
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 Cppcheck Plugin versions 1.26 and earlier fails to sanitize file names from Cppcheck report files before rendering them in the Jenkins UI. An attacker who can influence report file contents can inject malicious JavaScript code that executes in the browsers of users viewing the report, resulting in stored XSS.
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
CppcheckApplication
<= 1.26CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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.
-
Confirm Cppcheck Plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed and search for 'Cppcheck' in the list of installed plugins.Affected if The Cppcheck plugin appears in the installed plugins list.
-
Determine the installed Cppcheck plugin versionIn the Installed Plugins page, locate the Cppcheck plugin and note the version number displayed in the 'Version' column.Affected if The installed version is 1.26 or earlier.
-
Identify Cppcheck report usage in jobsReview Jenkins jobs that use the Cppcheck plugin by checking job configurations for 'Cppcheck' as a build step or post-build action. Identify any jobs that process Cppcheck XML report files.Affected if Jobs exist that import or display Cppcheck reports in Jenkins.
-
Inspect stored Cppcheck report files for malicious contentLocate Cppcheck report files in Jenkins workspaces or archived artifacts. Search the XML files for filename elements containing script tags, javascript: URIs, or other suspicious JavaScript code patterns.Affected if Any Cppcheck report files contain unsanitized script injection in filename fields.
A user is affected if the Cppcheck Plugin version is 1.26 or earlier and their Jenkins environment processes Cppcheck reports where attackers could inject malicious JavaScript into file name fields.
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 the Cppcheck Plugin to version 1.27 or later, which implements proper output encoding for file names. If upgrade is not immediately possible, restrict access to who can upload/create Cppcheck report files and review existing reports for suspicious content.
Cppcheck Plugin version 1.27 or later
- Navigate to Manage Jenkins > Manage Plugins
- Go to the 'Updates' tab
- Locate the Cppcheck Plugin in the list
- Click 'Update' to install the latest version (version 1.27 or later)
- Restart Jenkins if prompted or manually restart to ensure the update is fully applied
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Cppcheck
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2023-28678 — 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-2023-28678 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