# CVE-2019-0018: Juniper ATP: Persistent Cross-Site Scripting (XSS) vulnerability in file upload menu

> Authenticated users can inject scripts via file upload to steal admin credentials and perform unauthorized actions on Juniper ATP devices.

- **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:** No
- **Published:** 15 Jan 2019
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-64q2-7r9m-7p7x

## What is CVE-2019-0018?

CVE-2019-0018 is a medium-severity cross-site scripting vulnerability in Juniper ATP, published on 15 Jan 2019. 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 persistent cross-site scripting (XSS) vulnerability in the file upload menu of Juniper ATP may allow an authenticated user to inject arbitrary scripts and steal sensitive data and credentials from a web administration session, possibly tricking a follow-on administrative user to perform administrative actions on the device. This issue affects Juniper ATP 5.0 versions prior to 5.0.3.

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

## Which versions are affected by CVE-2019-0018?

It affects 1 product.


Products: Juniper Advanced Threat Prevention.

## How do I fix CVE-2019-0018?

No fix has been published for CVE-2019-0018 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-0018 being exploited?

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

## Other vulnerabilities in Juniper ATP

- [CVE-2019-0020](https://insights.sbomify.com/CVE-2019-0020/): Juniper ATP: Hard coded credentials used in Web Collector (critical 10.0)
- [CVE-2019-0022](https://insights.sbomify.com/CVE-2019-0022/): Hardcoded credentials in Juniper ATP (critical 10.0)
- [CVE-2019-0029](https://insights.sbomify.com/CVE-2019-0029/): Juniper ATP: Splunk credentials are in logged in clear text (high 8.8)
- [CVE-2019-0004](https://insights.sbomify.com/CVE-2019-0004/): Juniper ATP: API and device keys are logged in a world-readable permissions file (high 7.8)
- [CVE-2019-0021](https://insights.sbomify.com/CVE-2019-0021/): Juniper ATP: secret CLI inputs are logged to /var/log/syslog in clear text (high 7.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-0018 and fix it if it is affected.

What it is: CVE-2019-0018 is a medium-severity cross-site scripting vulnerability in Juniper ATP, published on 15 Jan 2019. 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-2019-0018 in the wild and no public exploit code.

Affected product: Juniper ATP. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-2019-0018/ (Markdown: https://insights.sbomify.com/CVE-2019-0018/index.md)
```

## Sources

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

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