CVE-2006-7199
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedEMC 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."
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceEMC RSA Security SiteKey contains a vulnerability where a remote attacker can perform a man-in-the-middle attack by operating a proxy server that relays authentication data between the victim and the legitimate SiteKey server. This allows the attacker to display the user's pre-selected verification image, defeating the intended security control that was designed to verify the server's identity to the user.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- M
- Authentication
- Single
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/Au:S/C:C/I:C/A:C
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if RSA SiteKey is deployedCheck your environment for installations or services related to EMC RSA Security SiteKey authentication. Look for SiteKey servers, associated web applications using SiteKey for login, or SiteKey configuration files in your authentication infrastructure.Affected if SiteKey is present in any capacity - all versions are affected by this vulnerability.
-
Verify authentication flow configurationReview the SiteKey authentication flow configuration to confirm it relies on the visual verification image (pre-selected verification image) as the primary server identity mechanism.Affected if The SiteKey implementation uses visual verification images for server authentication - this is the vulnerable mechanism.
-
Check for anti-relay protectionsInspect the SiteKey server configuration for the presence of cryptographic protections such as channel binding, certificate pinning, or transaction signing with unique session identifiers.Affected if No anti-relay protections are configured - the vulnerability exists when these mitigations are absent and the authentication can be proxied.
-
Test for proxy relay susceptibilityFrom an external or internal perspective, verify if authentication requests can be relayed through an intermediate proxy without the proxy being detected as an attack.Affected if Authentication traffic can be relayed through a proxy server while still presenting the legitimate user's expected verification image - this confirms the vulnerability is exploitable.
If EMC RSA Security SiteKey is deployed and the authentication flow relies on visual verification images without cryptographic anti-relay protections, the environment is vulnerable to the MITM attack described in this CVE.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement additional cryptographic protections in the SiteKey authentication flow to detect and prevent proxying/relay attacks, such as channel binding, certificate pinning, or transaction signing with unique session identifiers.
- Consultation8.0 h
- Implementation24.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-7199 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2006-7199 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data