# CVE-2011-3511: Privilege escalation in n/a

> Remote authenticated users can compromise integrity and availability in Oracle Database Server via Privileged Account vectors.

- **Severity:** Low 3.6 (`AV:N/AC:H/Au:S/C:N/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Oct 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-r282-wvr4-f4q9

## What is CVE-2011-3511?

CVE-2011-3511 is a low-severity vulnerability in Oracle Database Server, published on 18 Oct 2011. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Unspecified vulnerability in the Database Vault component in Oracle Database Server 10.2.0.3, 10.2.0.4, 10.2.0.5, 11.1.0.7, and 11.2.0.2 allows remote authenticated users to affect integrity and availability via unknown vectors related to Privileged Account.

## Which versions are affected by CVE-2011-3511?

It affects 1 product.


Products: Oracle Database Server.

## How do I fix CVE-2011-3511?

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

## Is CVE-2011-3511 being exploited?

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

What it is: CVE-2011-3511 is a low-severity vulnerability in Oracle Database Server, published on 18 Oct 2011. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2011-3511 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-2011-3511/ (Markdown: https://insights.sbomify.com/CVE-2011-3511/index.md)
```

## Sources

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

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