# CVE-2005-3448: Other in n/a

> Unspecified vulnerability in Oracle Application Server OC4J module with unknown impact and attack vectors.

- **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:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 2 Nov 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-f7r5-86hh-m6m6

## What is CVE-2005-3448?

CVE-2005-3448 is a critical vulnerability in Oracle Application Server, published on 2 Nov 2005. 

### Official description

Unspecified vulnerability in the OC4J Module in Oracle Application Server 9.0 up to 10.1.2.0.2 has unknown impact and attack vectors, as identified by Oracle Vuln# AS01.

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

It affects 1 product.


Products: Oracle Application Server.

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

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

## Is CVE-2005-3448 being exploited?

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

## Other vulnerabilities in Oracle Application Server

- [CVE-2008-1812](https://insights.sbomify.com/CVE-2008-1812/): Other in n/a (critical 10.0)
- [CVE-2008-1824](https://insights.sbomify.com/CVE-2008-1824/): Other in n/a (critical 10.0)
- [CVE-2008-0340](https://insights.sbomify.com/CVE-2008-0340/): Other in n/a (critical 10.0)
- [CVE-2008-0343](https://insights.sbomify.com/CVE-2008-0343/): Other in n/a (critical 10.0)
- [CVE-2008-0344](https://insights.sbomify.com/CVE-2008-0344/): Other in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-3448 and fix it if it is affected.

What it is: CVE-2005-3448 is a critical vulnerability in Oracle Application Server, published on 2 Nov 2005. 
Exploitation: There is no known exploitation of CVE-2005-3448 in the wild and no public exploit code.

Affected product: Oracle Application 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-3448/ (Markdown: https://insights.sbomify.com/CVE-2005-3448/index.md)
```

## Sources

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

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