# CVE-2017-10261: Information disclosure in Oracle Database

> A low-privileged attacker with logon access can exploit the XML Database component to gain unauthorized access to critical data.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Oct 2017
- **Updated:** 4 Oct 2024
- **Also known as:** GHSA-34j7-jj72-r63p

## What is CVE-2017-10261?

CVE-2017-10261 is a medium-severity vulnerability in Oracle Database, published on 19 Oct 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Vulnerability in the XML Database component of Oracle Database Server. Supported versions that are affected are 11.2.0.4 and 12.1.0.2. Easily exploitable vulnerability allows low privileged attacker having Create Session privilege with logon to the infrastructure where XML Database executes to compromise XML Database. While the vulnerability is in XML Database, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all XML Database accessible data. Note: This score is for Windows platform version 11.2.0.4 of Database. For Windows platform version 12.1.0.2 and Linux, the score is 5.5 with scope Unchanged. CVSS 3.0 Base Score 6.5 (Confidentiality impacts). CVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N).

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2017-10261?

It affects 1 product.


Products: Oracle Database.

## How do I fix CVE-2017-10261?

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

## Is CVE-2017-10261 being exploited?

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

## Other vulnerabilities in Oracle Database

- [CVE-2017-10202](https://insights.sbomify.com/CVE-2017-10202/): Privilege escalation in Oracle Database (critical 9.9)
- [CVE-2017-3310](https://insights.sbomify.com/CVE-2017-3310/): Privilege escalation in Oracle Database (critical 9.0)
- [CVE-2016-3609](https://insights.sbomify.com/CVE-2016-3609/): Other in n/a (critical 9.0)
- [CVE-2016-3454](https://insights.sbomify.com/CVE-2016-3454/): Other in n/a (critical 9.0)
- [CVE-2022-21510](https://insights.sbomify.com/CVE-2022-21510/): Privilege escalation in Database - Enterprise Edition (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-10261 and fix it if it is affected.

What it is: CVE-2017-10261 is a medium-severity vulnerability in Oracle Database, published on 19 Oct 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-10261 in the wild and no public exploit code.

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

## Sources

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

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