CVE-2011-2733
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 prevent reuse of authentication information during a session, which allows remote authenticated users to bypass intended access restrictions via vectors related to knowledge of the originally used authentication information and unspecified other session information.
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 prevent reuse of authentication information during an active session, allowing an authenticated attacker to leverage knowledge of original authentication credentials and session state to bypass intended access restrictions and escalate privileges within the session.
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
- Single
- Confidentiality
- Complete
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:S/C:C/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 RSA Adaptive Authentication On-Premise versionCheck the installed version by reviewing installation directories, version manifest files, or admin console 'About' section. Common paths include the application installation directory or check with vendor-specific version detection tools.Affected if The installed version is exactly 6.0.2.1 (this specific version is affected)
-
Locate session management configurationFind the session management configuration files in the application deployment directory. These are typically XML or properties files controlling session behavior, often under config/session or similar paths in the application root.Affected if Session configuration files exist and contain settings that allow credential replay within active sessions
-
Verify session-bound authentication validation settingsInspect session management configuration for whether authentication state is validated per-request or if cached credentials can be reused. Look for settings controlling credential reuse during active sessions.Affected if Authentication validation relies on cached or replayed credentials rather than current session state validation
-
Check authentication flow configurationReview authentication flow or security configuration files to determine if the system validates each session access against current authentication state or accepts previously authenticated credentials.Affected if The system accepts original authentication credentials without re-validating against current session state
A user is affected if they have RSA Adaptive Authentication On-Premise version 6.0.2.1 installed and the session configuration allows reuse of original authentication credentials during an active session rather than validating against current authentication state.
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 proper session-bound authentication validation that prevents reuse of authentication credentials and ensures each session access is validated against current authentication state rather than cached or replayed credentials.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.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 $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-2733 — 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-2733 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