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

> Remote authenticated users can obtain sensitive information from the archiver script in IBM WebSphere Partner Gateway.

- **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 May 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-xx89-xmcq-2q77

## What is CVE-2009-0897?

CVE-2009-0897 is a medium-severity vulnerability in n/a, published on 21 May 2009. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

IBM WebSphere Partner Gateway (WPG) 6.1.0 before 6.1.0.1 and 6.1.1 before 6.1.1.1 allows remote authenticated users to obtain sensitive information via vectors related to the "schema DB2 instance id" and the bcgarchive (aka the archiver script).

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

It affects 1 product.


Products: Ibm Websphere Partner Gateway.

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

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

## Is CVE-2009-0897 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-2093](https://insights.sbomify.com/CVE-2009-2093/): SQL injection in n/a (medium 6.5)
- [CVE-2009-0440](https://insights.sbomify.com/CVE-2009-0440/): Security feature bypass in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-0897 is a medium-severity vulnerability in n/a, published on 21 May 2009. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2009-0897 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-0897/ (Markdown: https://insights.sbomify.com/CVE-2009-0897/index.md)
```

## Sources

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

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