CVE-2012-2279
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 · uneditedOpen redirect vulnerability in the Security Console in EMC RSA Authentication Manager 7.1 before SP4 P14 and RSA SecurID Appliance 3.0 before SP4 P14 allows remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via unspecified vectors.
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 · high confidenceOpen redirect vulnerability in the Security Console of EMC RSA Authentication Manager 7.1 before SP4 P14 and RSA SecurID Appliance 3.0 before SP4 P14 allows remote attackers to redirect users to arbitrary websites via unspecified vectors, facilitating phishing attacks.
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<= 7.1= 7.0= 7.1= 7.1= 2.0= 2.0.1= 2.0.2= 3.0CVSS 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
- Low
- Authentication
- None
- Confidentiality
- None
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/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 the installed RSA productAccess the Security Console login page or check system documentation for the product name and base version (Authentication Manager or SecurID Appliance).Affected if The product is EMC RSA Authentication Manager 7.0/7.1 or RSA SecurID Appliance 2.0.x/3.0.
-
Check the Security Console version or patch levelLog into the Security Console and navigate to the About or System Information page to view the installed version and patch level.Affected if The patch level is shown but is below SP4 P14.
-
Verify the patch version via consoleWithin the Security Console, look for a patch or update status indicator that shows the current service pack and patch version installed.Affected if No patch information is displayed or the displayed patch is earlier than P14.
-
Confirm the version range matches vulnerable releasesCross-reference the identified base version and patch level against the affected ranges: Authentication Manager 7.0, 7.1 (any patch before SP4 P14) and SecurID Appliance 2.0, 2.0.1, 2.0.2, 3.0 (any patch before SP4 P14).Affected if The version is 7.0 or 7.1 without SP4 P14 applied, or the appliance is version 2.0.x/3.0 without SP4 P14 applied.
You are affected if the Security Console is running EMC RSA Authentication Manager 7.0/7.1 or RSA SecurID Appliance 2.0.x/3.0 and the installed patch level is earlier than SP4 P14.
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 vendor patch SP4 P14 (or later) to both RSA Authentication Manager and RSA SecurID Appliance. Until patched, users should verify URLs before clicking links originating from the Security Console.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-2279 — 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-2012-2279 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