# CVE-2020-2527: Information disclosure in Oracle Database

> High-privileged attackers can read unauthorized data in Oracle Database Core RDBMS via network access.

- **Severity:** Medium 4.1 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jan 2020
- **Updated:** 30 Sep 2024
- **Also known as:** GHSA-q6c7-8x78-93hx

## What is CVE-2020-2527?

CVE-2020-2527 is a medium-severity vulnerability in Oracle Database Server, published on 15 Jan 2020. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Vulnerability in the Core RDBMS component of Oracle Database Server. Supported versions that are affected are 12.1.0.2, 12.2.0.1, 18c and 19c. Easily exploitable vulnerability allows high privileged attacker having Create Index, Create Table privilege with network access via OracleNet to compromise Core RDBMS. While the vulnerability is in Core RDBMS, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized read access to a subset of Core RDBMS accessible data. CVSS 3.0 Base Score 4.1 (Confidentiality impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:N).

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

It affects 1 product.


Products: Oracle Database Server.

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

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

## Is CVE-2020-2527 being exploited?

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

## Other vulnerabilities in Oracle Database Server

- [CVE-2015-4863](https://insights.sbomify.com/CVE-2015-4863/): Other in n/a (critical 10.0)
- [CVE-2013-1534](https://insights.sbomify.com/CVE-2013-1534/): Other in n/a (critical 10.0)
- [CVE-2010-0071](https://insights.sbomify.com/CVE-2010-0071/): Other in n/a (critical 10.0)
- [CVE-2009-1979](https://insights.sbomify.com/CVE-2009-1979/): Other in n/a (critical 10.0)
- [CVE-2009-1985](https://insights.sbomify.com/CVE-2009-1985/): Other in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-2527 is a medium-severity vulnerability in Oracle Database Server, published on 15 Jan 2020. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-2527 in the wild and no public exploit code.

Affected product: Oracle Database Server. 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-2527/ (Markdown: https://insights.sbomify.com/CVE-2020-2527/index.md)
```

## Sources

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

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