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

> Attackers can obtain sensitive information from repositories due to improper security flag settings during migration in IBM WebSphere products.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Jun 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-rjqp-cxwg-rwxv

## What is CVE-2009-0899?

CVE-2009-0899 is a medium-severity vulnerability in Ibm Websphere Application Server, published on 3 Jun 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

IBM WebSphere Application Server (WAS) 6.1 through 6.1.0.24 and 7.0 through 7.0.0.4, IBM WebSphere Portal Server 5.1 through 6.0, and IBM Integrated Solutions Console (ISC) 6.0.1 do not properly set the IsSecurityEnabled security flag during migration of WebSphere Member Manager (WMM) to Virtual Member Manager (VMM) and a Federated Repository, which allows attackers to obtain sensitive information from repositories via unspecified vectors.

Weakness: CWE-264

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

It affects 3 products.


Products: Ibm Integrated Solutions Console, Ibm Websphere Application Server, Ibm Websphere Portal.

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

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

## Is CVE-2009-0899 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2009-0899 is a medium-severity vulnerability in Ibm Websphere Application Server, published on 3 Jun 2009. 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-2009-0899 in the wild and no public exploit code.

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

## Sources

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

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