Html PublisherApplication · Jenkins
CVE-2018-1000175
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 path traversal vulnerability exists in Jenkins HTML Publisher Plugin 1.15 and older in HtmlPublisherTarget.java that allows attackers able to configure the HTML Publisher build step to override arbitrary files on the Jenkins master.
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 path traversal vulnerability in Jenkins HTML Publisher Plugin 1.15 and older (in HtmlPublisherTarget.java) allows authenticated users with permissions to configure the HTML Publisher build step to write files to arbitrary locations on the Jenkins master, potentially overwriting configuration or system files.
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
Html PublisherApplication
<= 1.15CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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 HTML Publisher plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'HTML Publisher', or use the Jenkins CLI: java -jar jenkins-cli.jar list-plugins | findstr HTMLPublisherAffected if The plugin appears in the list of installed plugins
-
Check the installed version of HTML PublisherIn the Installed Plugins tab, look at the version column for HTML Publisher; or check the file $JENKINS_HOME/plugins/htmlpublisher.jpi for the version metadataAffected if The version is 1.15 or lower (1.15, 1.14, etc.)
-
Identify jobs using HTML Publisher build stepNavigate to each job's configuration page and look for the 'Publish HTML reports' build step under Build Steps, or search job config XML files in $JENKINS_HOME/jobs/ for '<htmlPublisher>Affected if Any job contains an HTML Publisher build step configuration
-
Audit HTML Publisher report directory pathsIn each job's configuration, examine the 'HTML directory to archive' and 'Report title' fields in the HTML Publisher section. Check if these paths use relative paths like '../' or absolute paths pointing outside the build workspaceAffected if The configuration contains paths that could escape the intended reports directory (e.g., paths using ../ or absolute paths to system directories)
-
Review user permissions for job configurationNavigate to Manage Jenkins > Manage and Assign Permissions. Check which users or groups have Job/Configure permission, particularly for jobs that use HTML PublisherAffected if Users with Job/Configure permission exist and HTML Publisher is in use, allowing them to exploit the path traversal
If the HTML Publisher plugin version is 1.15 or lower AND jobs using HTML Publisher exist with configurable report paths, the environment is vulnerable to this path traversal flaw.
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 the HTML Publisher plugin to version 1.16 or later, which contains the fix for this path traversal vulnerability. Review and audit existing job configurations for any malicious patterns.
Fix this in Html Publisher
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-2018-1000175 — 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-1000175 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