# CVE-2018-1000177: Stored XSS vulnerability in Jenkins S3 Publisher Plugin

> Attackers can execute arbitrary JavaScript in other users' browsers via malicious file names in the Jenkins S3 Plugin.

- **Severity:** Medium 5.4 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 8 May 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-3892-qqv6-h2qm

## What is CVE-2018-1000177?

CVE-2018-1000177 is a medium-severity cross-site scripting vulnerability in n/a, published on 8 May 2018. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A 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.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2018-1000177?

2 open source packages ship an affected version, including org.jenkins-ci.plugins:s3. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:s3` | Maven | All versions | 0.11.0 |
| `org.jenkins-ci.plugins:s3` | Maven | All versions | 0.11.0 |

Products: Jenkins S3 Publisher.

## How do I fix CVE-2018-1000177?

Upgrade org.jenkins-ci.plugins:s3 to 0.11.0 or later.

## Is CVE-2018-1000177 being exploited?

There is no known exploitation of CVE-2018-1000177 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2020-2114](https://insights.sbomify.com/CVE-2020-2114/): Jenkins S3 Publisher Plugin transmits credentials in plain text during configuration (high 7.5)
- [CVE-2021-21650](https://insights.sbomify.com/CVE-2021-21650/): Missing Authorization in Jenkins S3 publisher Plugin (medium 4.3)
- [CVE-2021-21651](https://insights.sbomify.com/CVE-2021-21651/): Missing Authorization in Jenkins S3 publisher Plugin (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-1000177 and fix it if it is affected.

What it is: CVE-2018-1000177 is a medium-severity cross-site scripting vulnerability in n/a, published on 8 May 2018. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-1000177 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:s3 (Maven): affected all versions; fixed in 0.11.0
- org.jenkins-ci.plugins:s3 (Maven): affected all versions; fixed in 0.11.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-1000177/ (Markdown: https://insights.sbomify.com/CVE-2018-1000177/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-1000177
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-1000177
- OSV: https://osv.dev/vulnerability/CVE-2018-1000177

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-1000177/
Summaries are generated and may contain mistakes; the official description above is the record.