# CVE-2008-2604: Auth bypass in n/a

> An unspecified vulnerability in the Oracle Database Authentication component allows remote authenticated attackers to bypass security controls.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:P`)
- **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:** 15 Jul 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-xj96-hvw8-2mj2

## What is CVE-2008-2604?

CVE-2008-2604 is a medium-severity authentication bypass vulnerability in Oracle Database Server, published on 15 Jul 2008. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Unspecified vulnerability in the Authentication component in Oracle Database 11.1.0.6 has unknown impact and remote authenticated attack vectors, a different vulnerability than CVE-2008-2605.

## Which versions are affected by CVE-2008-2604?

It affects 2 products.


Products: Oracle Authentication Component, Oracle Database Server.

## How do I fix CVE-2008-2604?

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

## Is CVE-2008-2604 being exploited?

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

## Other vulnerabilities in Oracle Database Server

- [CVE-2008-2605](https://insights.sbomify.com/CVE-2008-2605/): Auth bypass in n/a (medium 4.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-2604 and fix it if it is affected.

What it is: CVE-2008-2604 is a medium-severity authentication bypass vulnerability in Oracle Database Server, published on 15 Jul 2008. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2008-2604 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-2008-2604/ (Markdown: https://insights.sbomify.com/CVE-2008-2604/index.md)
```

## Sources

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

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