# CVE-2009-1979: Other in n/a

> Remote attackers can compromise Oracle Database confidentiality, integrity, and availability, potentially achieving arbitrary code execution via the Network Authentication component.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Oct 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-p54g-mf9q-782r

## What is CVE-2009-1979?

CVE-2009-1979 is a critical vulnerability in Oracle Database Server, published on 22 Oct 2009. It can be exploited over the network, with no action from the victim.

### Official description

Unspecified vulnerability in the Network Authentication component in Oracle Database 10.1.0.5 and 10.2.0.4 allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors.  NOTE: the previous information was obtained from the October 2009 CPU.  Oracle has not commented on claims from an independent researcher that this is related to improper validation of the AUTH_SESSKEY parameter length that leads to arbitrary code execution.

## Which versions are affected by CVE-2009-1979?

It affects 1 product.


Products: Oracle Database Server.

## How do I fix CVE-2009-1979?

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

## Is CVE-2009-1979 being exploited?

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

Public exploit code:

- Oracle 10gR2 TNS Listener AUTH_SESSKEY Buffer Overflow (metasploit)
- Oracle Database 10.1.0.5 < 10.2.0.4 - AUTH_SESSKEY Length Validation Remote Buffer Overflow (exploitdb)
- Oracle 10gR2 - TNS Listener AUTH_SESSKEY Buffer Overflow (Metasploit) (exploitdb)

## 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-1985](https://insights.sbomify.com/CVE-2009-1985/): Other in n/a (critical 10.0)
- [CVE-2009-1992](https://insights.sbomify.com/CVE-2009-1992/): Other in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-1979 and fix it if it is affected.

What it is: CVE-2009-1979 is a critical vulnerability in Oracle Database Server, published on 22 Oct 2009. It can be exploited over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-1979 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-2009-1979/ (Markdown: https://insights.sbomify.com/CVE-2009-1979/index.md)
```

## Sources

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

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