# CVE-2012-1675: Missing authorization in n/a

> Remote attackers can hijack database connections via TNS Poison to execute arbitrary commands and read data without authentication.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 May 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-xwqx-h938-xp3h

## What is CVE-2012-1675?

CVE-2012-1675 is a high-severity missing authorization vulnerability in Oracle Database Server, published on 8 May 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The TNS Listener, as used in Oracle Database 11g 11.1.0.7, 11.2.0.2, and 11.2.0.3, and 10g 10.2.0.3, 10.2.0.4, and 10.2.0.5, as used in Oracle Fusion Middleware, Enterprise Manager, E-Business Suite, and possibly other products, allows remote attackers to execute arbitrary database commands by performing a remote registration of a database (1) instance or (2) service name that already exists, then conducting a man-in-the-middle (MITM) attack to hijack database connections, aka "TNS Poison."

Weakness: CWE-264

## Which versions are affected by CVE-2012-1675?

It affects 1 product.


Products: Oracle Database Server.

## How do I fix CVE-2012-1675?

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

## Is CVE-2012-1675 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2012-1675 exists.

Public exploit code:

- Oracle Database TNS Listener Poison Attack Vulnerability (github_poc): https://github.com/bongbongco/CVE-2012-1675
- Oracle TNS Listener Checker (metasploit)

## 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-2012-1675 and fix it if it is affected.

What it is: CVE-2012-1675 is a high-severity missing authorization vulnerability in Oracle Database Server, published on 8 May 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2012-1675 exists.

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-2012-1675/ (Markdown: https://insights.sbomify.com/CVE-2012-1675/index.md)
```

## Sources

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

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