# CVE-2006-7199: Security feature bypass in n/a

> Attackers can bypass RSA SiteKey visual authentication via man-in-the-middle proxying, allowing them to display legitimate images to users.

- **Severity:** High 8.5 (`AV:N/AC:M/Au:S/C:C/I:C/A:C`)
- **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:** 30 Apr 2007
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-8xpc-fq47-wxcp

## What is CVE-2006-7199?

CVE-2006-7199 is a high-severity vulnerability in n/a, published on 30 Apr 2007. 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

EMC RSA Security SiteKey allows remote attackers to display the correct image via a man-in-the-middle (MITM) attack in which an attacker-controlled server proxies authentication data to and from a legitimate SiteKey server.  NOTE: the vendor disputes the severity of the issue, stating that it is easier to monitor this attack than "attacks against static web pages."

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

It affects 1 product.


Products: Emc Rsa Security Sitekey.

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

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

## Is CVE-2006-7199 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-7201](https://insights.sbomify.com/CVE-2006-7201/): Information disclosure in n/a (critical 9.3)
- [CVE-2006-7200](https://insights.sbomify.com/CVE-2006-7200/): Auth bypass in n/a (critical 9.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-7199 is a high-severity vulnerability in n/a, published on 30 Apr 2007. 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-7199 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-7199/ (Markdown: https://insights.sbomify.com/CVE-2006-7199/index.md)
```

## Sources

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

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