Cucumber Living DocumentationApplication · Jenkins
CVE-2018-1000144
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 Cucumber Living Documentation Plugin 1.0.12 and older in CukedoctorBaseAction#doDynamic that disables the Content-Security-Policy protection for archived artifacts and workspace files, allowing attackers able to control the content of these files to attack Jenkins users.
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 confidenceCross-site scripting vulnerability in Jenkins Cucumber Living Documentation Plugin where the CukedoctorBaseAction#doDynamic method disables Content-Security-Policy protection for archived artifacts and workspace files, allowing attackers who control file content to inject malicious scripts that execute in Jenkins user browsers.
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
Cucumber Living DocumentationApplication
<= 1.0.12CVSS 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.
-
Identify if Cucumber Living Documentation Plugin is installedIn Jenkins, go to Manage Jenkins > Manage Plugins > Installed tab and search for 'Cucumber Living Documentation' or 'Cukedoctor', or inspect the file system at $JENKINS_HOME/plugins/ for a directory named 'cucumber-living-documentation' or 'cukedoctor'Affected if The plugin is present in the installed plugins list or plugin directory
-
Determine the installed plugin versionIf the plugin is present, check its version by inspecting the plugin manifest: in $JENKINS_HOME/plugins/[plugin-dir]/META-INF/MANIFEST.MF for the 'Implementation-Version' attribute, or inspect the .jpi file's plugin metadataAffected if The version is 1.0.12 or lower (the vulnerable range)
-
Verify the vulnerable endpoint is accessibleConfirm the CukedoctorBaseAction dynamic endpoint is available by attempting to access a URL pattern like /jenkins/plugin/cucumber-living-documentation/doDynamic or checking if the plugin's web.xml defines the CukedoctorBaseAction servlet mappingAffected if The doDynamic method responds without Content-Security-Policy headers restricting script execution
-
Check for archived artifacts or workspace filesInspect whether archived artifacts or workspace files exist in Jenkins that could be served through the plugin's endpoint. Review content accessible via /jenkins/artifact/ or workspace URLs that the plugin may serveAffected if There are archived artifacts or workspace files that can be accessed through the plugin's dynamic endpoint without CSP headers
A user is affected if the Cucumber Living Documentation Plugin version 1.0.12 or lower is installed and the plugin serves archived artifacts or workspace files through its dynamic endpoint, allowing script injection due to missing Content-Security-Policy protection.
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 Cucumber Living Documentation Plugin version 1.0.13 or later, which contains the fix to restore proper Content-Security-Policy headers. If upgrade is not possible, restrict permissions to prevent untrusted users from uploading controlled content to workspaces or archives.
Fix this in Cucumber Living Documentation
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1000144 — 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-1000144 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