# CVE-2019-10180: Cross-site scripting in pki-core

> An attacker can inject malicious JavaScript into token parameters, tricking authenticated users into executing arbitrary code.

- **Severity:** Low 2.4 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 31 Mar 2020
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2019-10180, GHSA-3r6g-5p5v-m39h, UBUNTU-CVE-2019-10180

## What is CVE-2019-10180?

CVE-2019-10180 is a low-severity cross-site scripting vulnerability in [UNKNOWN] pki-core, published on 31 Mar 2020. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

A vulnerability was found in all pki-core 10.x.x version, where the Token Processing Service (TPS) did not properly sanitize several parameters stored for the tokens, possibly resulting in a Stored Cross Site Scripting (XSS) vulnerability. An attacker able to modify the parameters of any token could use this flaw to trick an authenticated user into executing arbitrary JavaScript code.

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

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

It affects 2 products.


Products: Dogtagpki Dogtagpki, Redhat Certificate System.

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

Apply the vendor's patch.

## Is CVE-2019-10180 being exploited?

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

## Other vulnerabilities in [UNKNOWN] pki-core

- [CVE-2021-20179](https://insights.sbomify.com/CVE-2021-20179/): Business logic in pki-core (high 8.1)
- [CVE-2021-3551](https://insights.sbomify.com/CVE-2021-3551/): Information disclosure in pki-server (high 7.8)
- [CVE-2022-2414](https://insights.sbomify.com/CVE-2022-2414/): XML external entity in Dogtag PKI (high 7.5)
- [CVE-2018-1080](https://insights.sbomify.com/CVE-2018-1080/): Auth bypass in pki-core (high 7.5)
- [CVE-2020-15720](https://insights.sbomify.com/CVE-2020-15720/): Security feature bypass in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-10180 is a low-severity cross-site scripting vulnerability in [UNKNOWN] pki-core, published on 31 Mar 2020. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-10180 in the wild and no public exploit code.

Affected product: [UNKNOWN] pki-core. 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-10180/ (Markdown: https://insights.sbomify.com/CVE-2019-10180/index.md)
```

## Sources

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

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