S3 PublisherApplication · Jenkins
CVE-2018-1000177
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 S3 Plugin 0.10.12 and older in src/main/resources/hudson/plugins/s3/S3ArtifactsProjectAction/jobMain.jelly that allows attackers able to control file names of uploaded files to define file names containing JavaScript that would be executed in another user's browser when that user performs some UI actions.
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 stored cross-site scripting vulnerability in Jenkins S3 Plugin versions 0.10.12 and older allows attackers to inject malicious JavaScript into file names displayed in the S3 artifacts project action UI (jobMain.jelly). When other users view the artifact list, the unsanitized file name is rendered, executing the attacker's JavaScript in their browser session.
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
S3 PublisherApplication
<= 0.10.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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/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.
-
Verify Jenkins S3 Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and look for 'S3' or 'AWS S3 Plugin' in the list, or run: jenkins-cli.jar who-am-i (or check $JENKINS_HOME/plugins for s3-plugin directoryAffected if The S3 Plugin is not installed - you are not affected
-
Determine the installed S3 Plugin versionIn the Installed Plugins tab, find the S3 Plugin and note the Version column; or check the version file in $JENKINS_HOME/plugins/s3/WEB-INF/detached-plugins (if available)Affected if Version is 0.10.12 or older - you may be affected; version 0.10.13 or later includes the fix
-
Identify jobs using S3 artifact publishingSearch job configurations for 'S3' or 'Amazon S3' post-build actions, or inspect $JENKINS_HOME/jobs/*/config.xml for <s3> publisher entriesAffected if No jobs configure S3 artifact storage - the attack surface does not exist in your environment
-
Inspect S3 artifact file names for unsanitized contentIf jobs use S3 publishing, examine the file names stored in the S3 bucket and check if they contain HTML/JavaScript tags like <script>, javascript:, or event handlers (onclick, onerror, etc.)Affected if S3 artifacts contain file names with unsanitized HTML/script content that could execute in a browser
You are affected if the S3 Plugin version is 0.10.12 or older AND you have jobs configured to publish artifacts to S3, since the vulnerability requires both the vulnerable plugin and the S3 publishing feature to be active.
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 Jenkins S3 Plugin to version 0.10.13 or later, which should include proper output encoding for file names in the jobMain.jelly template.
Fix this in S3 Publisher
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1000177 — 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-1000177 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