# CVE-2005-3641: Auth bypass in n/a

> Remote attackers can bypass authentication on Oracle Databases on Windows XP if Simple File Sharing is enabled.

- **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:** 16 Nov 2005
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-cp75-c7h5-j538

## What is CVE-2005-3641?

CVE-2005-3641 is a high-severity authentication bypass vulnerability in Oracle Database Server, published on 16 Nov 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Oracle Databases running on Windows XP with Simple File Sharing enabled, allows remote attackers to bypass authentication by supplying a valid username.

## Which versions are affected by CVE-2005-3641?

It affects 5 products.


Products: Oracle Database Server, Oracle Database Server Lite, Oracle Oracle10g, Oracle Oracle8i, Oracle Oracle9i.

## How do I fix CVE-2005-3641?

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

## Is CVE-2005-3641 being exploited?

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

What it is: CVE-2005-3641 is a high-severity authentication bypass vulnerability in Oracle Database Server, published on 16 Nov 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-3641 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-2005-3641/ (Markdown: https://insights.sbomify.com/CVE-2005-3641/index.md)
```

## Sources

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

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