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

> A low-privileged local attacker can exploit a vulnerability in Oracle Database to gain unauthorized read access to sensitive security data.

- **Severity:** Low 3.3 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/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:** 27 Jan 2017
- **Updated:** 9 Oct 2024
- **Also known as:** GHSA-c96v-9339-qhf6

## What is CVE-2017-3240?

CVE-2017-3240 is a low-severity vulnerability in Oracle Database Server, published on 27 Jan 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Vulnerability in the RDBMS Security component of Oracle Database Server. The supported version that is affected is 12.1.0.2. Easily exploitable vulnerability allows low privileged attacker having Local Logon privilege with logon to the infrastructure where RDBMS Security executes to compromise RDBMS Security. Successful attacks of this vulnerability can result in unauthorized read access to a subset of RDBMS Security accessible data. CVSS v3.0 Base Score 3.3 (Confidentiality impacts).

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

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

It affects 1 product.


Products: Oracle Database Server.

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

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

## Is CVE-2017-3240 being exploited?

There is no known exploitation of CVE-2017-3240 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-2017-3240 and fix it if it is affected.

What it is: CVE-2017-3240 is a low-severity vulnerability in Oracle Database Server, published on 27 Jan 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-3240 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-2017-3240/ (Markdown: https://insights.sbomify.com/CVE-2017-3240/index.md)
```

## Sources

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

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