# CVE-2006-5161: Information disclosure in n/a

> Remote attackers can steal saved credentials by spoofing website titles, exposing sensitive user data in IBM Client Security Password Manager.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 3 Oct 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-3gpc-q28p-x5wq

## What is CVE-2006-5161?

CVE-2006-5161 is a medium-severity vulnerability in n/a, published on 3 Oct 2006. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

IBM Client Security Password Manager stores and distributes saved passwords based upon the title of a website, which allows remote attackers to obtain username and password credentials by changing the title of an HTML page.

## Which versions are affected by CVE-2006-5161?

It affects 1 product.


Products: Ibm Client Security Password Manager.

## How do I fix CVE-2006-5161?

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

## Is CVE-2006-5161 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-5161 and fix it if it is affected.

What it is: CVE-2006-5161 is a medium-severity vulnerability in n/a, published on 3 Oct 2006. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2006-5161 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-2006-5161/ (Markdown: https://insights.sbomify.com/CVE-2006-5161/index.md)
```

## Sources

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

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