# CVE-2002-0228: Information disclosure in n/a

> Remote attackers can exploit ActiveX objects in MSN Messenger to steal sensitive user information like display names and navigation data.

- **Severity:** Medium 5.0 (`AV:N/AC:L/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 3 May 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-jvcw-7829-ggcr

## What is CVE-2002-0228?

CVE-2002-0228 is a medium-severity vulnerability in n/a, published on 3 May 2002. 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

Microsoft MSN Messenger allows remote attackers to use Javascript that references an ActiveX object to obtain sensitive information such as display names and web site navigation, and possibly more when the user is connected to certain Microsoft sites (or DNS-spoofed sites).

## Which versions are affected by CVE-2002-0228?

It affects 1 product.


Products: Microsoft Msn Messenger.

## How do I fix CVE-2002-0228?

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

## Is CVE-2002-0228 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-2931](https://insights.sbomify.com/CVE-2007-2931/): Memory corruption in n/a (critical 9.3)
- [CVE-2005-0562](https://insights.sbomify.com/CVE-2005-0562/): Memory corruption in n/a (high 7.5)
- [CVE-2007-3436](https://insights.sbomify.com/CVE-2007-3436/): Denial of service in n/a (medium 5.0)
- [CVE-2002-1831](https://insights.sbomify.com/CVE-2002-1831/): Denial of service in n/a (medium 5.0)
- [CVE-2002-1698](https://insights.sbomify.com/CVE-2002-1698/): Memory corruption in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-0228 and fix it if it is affected.

What it is: CVE-2002-0228 is a medium-severity vulnerability in n/a, published on 3 May 2002. 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-2002-0228 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-2002-0228/ (Markdown: https://insights.sbomify.com/CVE-2002-0228/index.md)
```

## Sources

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

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