# CVE-2004-2635: Information disclosure in n/a

> Remote attackers can read Windows registry data via a vulnerable ActiveX control in McAfee Security Installer, requiring user interaction to visit a malicious webpage.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **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:** 4 Dec 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-x85h-h5r6-5rh8

## What is CVE-2004-2635?

CVE-2004-2635 is a high-severity vulnerability in n/a, published on 4 Dec 2005. 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

An ActiveX control for McAfee Security Installer Control System 4.0.0.81 allows remote attackers to access the Windows registry via web pages that use the control's RegQueryValue() method.

## Which versions are affected by CVE-2004-2635?

It affects 1 product.


Products: Mcafee Security Installer Control System.

## How do I fix CVE-2004-2635?

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

## Is CVE-2004-2635 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-2635 and fix it if it is affected.

What it is: CVE-2004-2635 is a high-severity vulnerability in n/a, published on 4 Dec 2005. 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-2004-2635 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-2004-2635/ (Markdown: https://insights.sbomify.com/CVE-2004-2635/index.md)
```

## Sources

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

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