CVE-2011-2742
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 Adaptive Authentication On-Premise (AAOP) 6.0.2.1 SP1 Patch 2, SP1 Patch 3, SP2, SP2 Patch 1, and SP3 does not properly perform forensic evaluation upon receipt of device tokens from mobile apps, which might allow remote attackers to bypass intended application restrictions via a mobile device.
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 Adaptive Authentication On-Premise fails to properly perform forensic evaluation when receiving device tokens from mobile applications. This allows remote attackers to bypass intended application restrictions by exploiting insufficient validation of mobile device tokens during the authentication process.
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 data= 6.0.2.1CVSS 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
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
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 installed RSA Adaptive Authentication versionLocate the version of EMC RSA Adaptive Authentication On-Premise installed in your environment. This is typically found in the product documentation, installation files, or administrative console under system information or about sections.Affected if The installed version is exactly 6.0.2.1
-
Determine if mobile application authentication is enabledCheck the RSA Adaptive Authentication administrative console or configuration files for settings related to mobile application authentication, mobile device access, or mobile app integration features.Affected if Mobile application authentication features are enabled and the version is 6.0.2.1
-
Verify device token processing configurationInspect the configuration settings that govern how device tokens from mobile applications are processed during authentication. Look for settings related to device token validation, forensic evaluation, or mobile device trust assessment.Affected if Device token processing is active and the version is 6.0.2.1
-
Review forensic evaluation settings for mobile devicesExamine the forensic evaluation or device fingerprinting configuration specifically for mobile device tokens. Check whether mobile device token validation is set to validate authenticity before granting access.Affected if Forensic evaluation for mobile device tokens is configured and the version is 6.0.2.1
You are affected if RSA Adaptive Authentication On-Premise version 6.0.2.1 is installed and mobile application authentication with device token processing is enabled in your environment.
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 dataApply the vendor patch for this vulnerability and verify that mobile device token forensic evaluation now correctly validates device authenticity before granting access. Consider additional compensating controls such as multi-factor authentication for mobile app access.
- Consultation6.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,296.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-2742 — 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-2011-2742 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