# CVE-2020-6254: Cross-site scripting in SAP Enterprise Threat Detection

> Reflected Cross-Site Scripting in SAP Enterprise Threat Detection allows attackers to execute arbitrary scripts in victim browsers via crafted error responses.

- **Severity:** Medium 6.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 May 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-xq2c-xc9f-44f4

## What is CVE-2020-6254?

CVE-2020-6254 is a medium-severity cross-site scripting vulnerability in SAP Enterprise Threat Detection, published on 12 May 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

SAP Enterprise Threat Detection, versions 1.0, 2.0, does not sufficiently encode error response pages in case of errors, allowing XSS payload reflecting in the response, leading to reflected Cross Site Scripting.

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

## Which versions are affected by CVE-2020-6254?

It affects 1 product.


Products: Sap Enterprise Threat Detection.

## How do I fix CVE-2020-6254?

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

## Is CVE-2020-6254 being exploited?

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

## Other vulnerabilities in SAP Enterprise Threat Detection

- [CVE-2022-22529](https://insights.sbomify.com/CVE-2022-22529/): Cross-site scripting in SAP Enterprise Threat Detection (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-6254 and fix it if it is affected.

What it is: CVE-2020-6254 is a medium-severity cross-site scripting vulnerability in SAP Enterprise Threat Detection, published on 12 May 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-6254 in the wild and no public exploit code.

Affected product: SAP Enterprise Threat Detection. 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-2020-6254/ (Markdown: https://insights.sbomify.com/CVE-2020-6254/index.md)
```

## Sources

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

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