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

> Remote attackers can compromise confidentiality, integrity, and availability in the JRockit component of the BEA Product Suite via unspecified 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:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 22 Oct 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-9r76-mhm8-f3q4

## What is CVE-2009-3403?

CVE-2009-3403 is a critical vulnerability in n/a, published on 22 Oct 2009. It can be exploited over the network.

### Official description

Unspecified vulnerability in the JRockit component in BEA Product Suite R27.6.4: JRE/JDK, 1.4.2, 5, and, and 6 allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors.  NOTE: this issue subsumes CVE-2009-2670, CVE-2009-2671, CVE-2009-2672, CVE-2009-2673, CVE-2009-2674, CVE-2009-2675, and CVE-2009-2676.

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

It affects 1 product.


Products: Oracle Bea Product Suite.

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

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

## Is CVE-2009-3403 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-0079](https://insights.sbomify.com/CVE-2010-0079/): Other in n/a (critical 10.0)
- [CVE-2009-1012](https://insights.sbomify.com/CVE-2009-1012/): Integer overflow in n/a (critical 10.0)
- [CVE-2008-5457](https://insights.sbomify.com/CVE-2008-5457/): Other in n/a (critical 10.0)
- [CVE-2008-4008](https://insights.sbomify.com/CVE-2008-4008/): Memory corruption in n/a (critical 10.0)
- [CVE-2009-1016](https://insights.sbomify.com/CVE-2009-1016/): Memory corruption in n/a (high 8.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-3403 is a critical vulnerability in n/a, published on 22 Oct 2009. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2009-3403 in the wild and no public exploit code.

Affected product: n/a. 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-3403/ (Markdown: https://insights.sbomify.com/CVE-2009-3403/index.md)
```

## Sources

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

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