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

> Local attackers can steal sensitive cookies and credentials by tricking users into clicking links that send data to attacker-controlled ports.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 28 Feb 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-rw8p-9rcw-27w7

## What is CVE-2006-0917?

CVE-2006-0917 is a low-severity vulnerability in n/a, published on 28 Feb 2006. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Melange Chat Server (aka M-Chat), when accessed via a web browser, automatically sends cookies and other sensitive information for a server to any port specified in the associated link, which allows local users on that server to read the cookies from HTTP headers and possibly gain sensitive information, such as credentials, by setting up a listening port and reading the credentials when the victim clicks on the link.

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

It affects 1 product.


Products: Melange Melange Chat System.

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

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

## Is CVE-2006-0917 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2002-0552](https://insights.sbomify.com/CVE-2002-0552/): Memory corruption in n/a (high 7.5)
- [CVE-2002-1351](https://insights.sbomify.com/CVE-2002-1351/): Memory corruption in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-0917 is a low-severity vulnerability in n/a, published on 28 Feb 2006. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2006-0917 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-0917/ (Markdown: https://insights.sbomify.com/CVE-2006-0917/index.md)
```

## Sources

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

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