# CVE-2018-3253: Missing authorization in Virtual Directory

> Low-privileged attackers can compromise Oracle Virtual Directory to read, modify, or delete data and cause partial denial of service.

- **Severity:** High 8.5 (`CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Oct 2018
- **Updated:** 2 Oct 2024
- **Also known as:** GHSA-fww5-xv47-fvxx

## What is CVE-2018-3253?

CVE-2018-3253 is a high-severity missing authorization vulnerability in Oracle Corporation Virtual Directory, published on 17 Oct 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Vulnerability in the Oracle Virtual Directory component of Oracle Fusion Middleware (subcomponent: Virtual Directory Manager). Supported versions that are affected are 11.1.1.7.0 and 11.1.1.9.0. Difficult to exploit vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Virtual Directory. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Virtual Directory accessible data as well as unauthorized read access to a subset of Oracle Virtual Directory accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle Virtual Directory. CVSS 3.0 Base Score 8.5 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H).

## Which versions are affected by CVE-2018-3253?

It affects 1 product.


Products: Oracle Virtual Directory.

## How do I fix CVE-2018-3253?

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

## Is CVE-2018-3253 being exploited?

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

## Other vulnerabilities in Oracle Corporation Virtual Directory

- [CVE-2026-35312](https://insights.sbomify.com/CVE-2026-35312/): Auth bypass in Oracle Virtual Directory (critical 9.8)
- [CVE-2026-61231](https://insights.sbomify.com/CVE-2026-61231/): Privilege escalation in Oracle Virtual Directory (high 8.8)
- [CVE-2017-10369](https://insights.sbomify.com/CVE-2017-10369/): Auth bypass in Oracle Virtual Directory (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-3253 and fix it if it is affected.

What it is: CVE-2018-3253 is a high-severity missing authorization vulnerability in Oracle Corporation Virtual Directory, published on 17 Oct 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-3253 in the wild and no public exploit code.

Affected product: Oracle Corporation Virtual Directory. 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-2018-3253/ (Markdown: https://insights.sbomify.com/CVE-2018-3253/index.md)
```

## Sources

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

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