# CVE-2009-1003: Information disclosure in n/a

> Remote attackers can access source code of web pages in WebLogic Server, compromising data integrity and confidentiality.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Apr 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-5g6f-xpmm-cp3m

## What is CVE-2009-1003?

CVE-2009-1003 is a medium-severity vulnerability in n/a, published on 15 Apr 2009. It can be exploited over the network, with no action from the victim.

### Official description

Unspecified vulnerability in the WebLogic Server component in BEA Product Suite 10.3, 10.0 MP1, 9.2 MP3, 9.1, and 9.0 allows remote attackers to affect integrity via unknown vectors related to "access to source code of web pages."

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

It affects 1 product.


Products: Oracle Bea Product Suite.

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

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

## Is CVE-2009-1003 being exploited?

There is no known exploitation of CVE-2009-1003 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-3403](https://insights.sbomify.com/CVE-2009-3403/): 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)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-1003 is a medium-severity vulnerability in n/a, published on 15 Apr 2009. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2009-1003 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-1003/ (Markdown: https://insights.sbomify.com/CVE-2009-1003/index.md)
```

## Sources

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

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