CppncssApplication · Jenkins
CVE-2018-1000108
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 · uneditedA cross-site scripting vulnerability exists in Jenkins CppNCSS Plugin 1.1 and earlier in AbstractProjectAction/index.jelly that allow an attacker to craft links to Jenkins URLs that run arbitrary JavaScript in the user's browser when accessed.
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 confidenceA cross-site scripting vulnerability in Jenkins CppNCSS Plugin 1.1 and earlier in AbstractProjectAction/index.jelly allows injection of malicious JavaScript through crafted URLs that execute in victims' browsers when accessed.
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
CppncssApplication
<= 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/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.
-
Verify CppNCSS plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, or check the $JENKINS_HOME/plugins directory for cppncss folderAffected if CppNCSS plugin appears in the installed plugins list
-
Determine installed CppNCSS plugin versionIn Jenkins > Manage Jenkins > Manage Plugins > Installed, find CppNCSS and note the version number displayed, or check the manifest file at $JENKINS_HOME/plugins/cppncss/META-INF/MANIFEST.MFAffected if Version is 1.1 or earlier, or version cannot be determined (plugin too old)
-
Confirm vulnerable component existsCheck if the file AbstractProjectAction/index.jelly exists in the plugin directory at $JENKINS_HOME/plugins/cppncss/WEB-INF/classes/hudson/plugins/cppncss/AbstractProjectAction/Affected if The index.jelly file exists in the expected location, indicating the vulnerable code path is present
-
Verify plugin is actively used in jobsReview Jenkins jobs to see if any projects have CppNCSS build actions enabled (check job configuration pages or inspect job config.xml files for <hudson.plugins.cppncss...> entries)Affected if Any job configuration references the CppNCSS plugin, meaning the vulnerable URL path could be accessed
If the CppNCSS plugin is installed at version 1.1 or earlier and is in use by any Jenkins jobs, the environment is affected by this XSS vulnerability.
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.
From vendor dataUpgrade to a patched version of the CppNCSS plugin; if no patch is available, disable or remove the plugin to eliminate the XSS attack vector.
Fix this in Cppncss
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1000108 — 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-2018-1000108 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