# CVE-2020-14787: Cross-site scripting in Communications Diameter Signaling Router (DSR)

> Low-privileged attackers can exploit a UI vulnerability in Oracle DSR to read and modify data via network access requiring user interaction.

- **Severity:** Medium 5.4 (`CVSS:3.1/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:** 21 Oct 2020
- **Updated:** 26 Sep 2024
- **Also known as:** GHSA-725w-grwp-vmm4

## What is CVE-2020-14787?

CVE-2020-14787 is a medium-severity cross-site scripting vulnerability in Oracle Communications Diameter Signaling Router, published on 21 Oct 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Vulnerability in the Oracle Communications Diameter Signaling Router (DSR) product of Oracle Communications (component: User Interface). Supported versions that are affected are 8.0.0.0-8.4.0.5. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Communications Diameter Signaling Router (DSR). Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Communications Diameter Signaling Router (DSR), attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Communications Diameter Signaling Router (DSR) accessible data as well as unauthorized read access to a subset of Oracle Communications Diameter Signaling Router (DSR) accessible data. CVSS 3.1 Base Score 5.4 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N).

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

It affects 1 product.


Products: Oracle Communications Diameter Signaling Router.

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

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

## Is CVE-2020-14787 being exploited?

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

## Other vulnerabilities in Oracle Communications Diameter Signaling Router

- [CVE-2017-9841](https://insights.sbomify.com/CVE-2017-9841/): PHPUnit Command Injection (critical 9.8, exploited in the wild)
- [CVE-2019-2729](https://insights.sbomify.com/CVE-2019-2729/): Auth bypass in WebLogic Server (critical 9.8)
- [CVE-2019-2399](https://insights.sbomify.com/CVE-2019-2399/): Information disclosure in Communications Diameter Signaling Router (DSR) (medium 6.5)
- [CVE-2020-14788](https://insights.sbomify.com/CVE-2020-14788/): Cross-site scripting in Communications Diameter Signaling Router (DSR) (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-14787 is a medium-severity cross-site scripting vulnerability in Oracle Communications Diameter Signaling Router, published on 21 Oct 2020. 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-2020-14787 in the wild and no public exploit code.

Affected product: Oracle Communications Diameter Signaling Router. 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-14787/ (Markdown: https://insights.sbomify.com/CVE-2020-14787/index.md)
```

## Sources

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

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