# CVE-2020-14630: Denial of service in Enterprise Session Border Controller

> High-privileged attackers can cause complete denial of service and unauthorized data access in Oracle Enterprise Session Border Controller via HTTP.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:H`)
- **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:** No
- **Published:** 15 Jul 2020
- **Updated:** 27 Sep 2024
- **Also known as:** GHSA-rc79-v6cr-35gr

## What is CVE-2020-14630?

CVE-2020-14630 is a high-severity denial of service vulnerability in Oracle Corporation Enterprise Session Border Controller, published on 15 Jul 2020. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Vulnerability in the Oracle Enterprise Session Border Controller product of Oracle Communications Applications (component: File Upload). Supported versions that are affected are 8.1.0, 8.2.0 and 8.3.0. Easily exploitable vulnerability allows high privileged attacker with network access via HTTP to compromise Oracle Enterprise Session Border Controller. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Enterprise Session Border Controller, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of Oracle Enterprise Session Border Controller as well as unauthorized update, insert or delete access to some of Oracle Enterprise Session Border Controller accessible data and unauthorized read access to a subset of Oracle Enterprise Session Border Controller accessible data. CVSS 3.1 Base Score 7.5 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:H).

Weakness: CWE-404 (Improper Resource Shutdown or Release)

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

It affects 1 product.


Products: Oracle Enterprise Session Border Controller.

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

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

## Is CVE-2020-14630 being exploited?

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

## Other vulnerabilities in Oracle Corporation Enterprise Session Border Controller

- [CVE-2022-21382](https://insights.sbomify.com/CVE-2022-21382/): Missing authorization in Enterprise Session Border Controller (high 7.7)
- [CVE-2022-21381](https://insights.sbomify.com/CVE-2022-21381/): Missing authorization in Enterprise Session Border Controller (medium 6.4)
- [CVE-2023-22083](https://insights.sbomify.com/CVE-2023-22083/): Information disclosure in Enterprise Communications Broker (medium 4.3)
- [CVE-2022-21383](https://insights.sbomify.com/CVE-2022-21383/): Denial of service in Enterprise Session Border Controller (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-14630 is a high-severity denial of service vulnerability in Oracle Corporation Enterprise Session Border Controller, published on 15 Jul 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-2020-14630 in the wild and no public exploit code.

Affected product: Oracle Corporation Enterprise Session Border Controller. 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-14630/ (Markdown: https://insights.sbomify.com/CVE-2020-14630/index.md)
```

## Sources

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

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