CVE-2012-2292
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 · uneditedThe Silverlight cross-domain policy in EMC RSA Archer SmartSuite Framework 4.x and RSA Archer GRC 5.x before 5.2SP1 does not restrict access to the Archer application, which allows remote attackers to bypass the Same Origin Policy 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 · moderate confidenceThe vulnerability exists in the Silverlight cross-domain policy of EMC RSA Archer SmartSuite Framework 4.x and RSA Archer GRC 5.x before 5.2SP1. The policy fails to restrict access to the Archer application, allowing remote attackers to bypass the Same Origin Policy through unspecified vectors. This enables malicious Silverlight applications hosted on other domains to make requests to the Archer application, potentially exposing sensitive data.
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= 4.3= 4.5= 5.0= 5.1= 5.2CVSS 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
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/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 RSA Archer versionCheck the installed RSA Archer version via the About page in the Archer web interface, or inspect the version file in the Archer installation directory (typically in the 'Help' or 'About' section).Affected if The installed version is 4.3, 4.5, 5.0, 5.1, or 5.2 (prior to Service Pack 1).
-
Locate clientaccesspolicy.xmlSearch for the file 'clientaccesspolicy.xml' in the web root of the RSA Archer application (commonly found in the '/' or '/Archer/' directory of the web server).Affected if The file exists in the web-accessible directory.
-
Examine clientaccesspolicy.xml contentsOpen and read clientaccesspolicy.xml. Look for the <access-policy> and <cross-domain-access> elements. Check if 'domain uri' is set to specific allowed domains or if it permits any domain access (often indicated by a wildcard or missing domain restrictions).Affected if The policy grants universal access (no domain restrictions) or permits access from untrusted domains.
-
Locate crossdomain.xmlSearch for the file 'crossdomain.xml' in the same web root location as clientaccesspolicy.xml.Affected if The file exists in the web-accessible directory.
-
Examine crossdomain.xml contentsOpen and read crossdomain.xml. Check the <allow-access-from> element to see if domain attributes are restricted to specific trusted domains or allow all domains.Affected if The policy permits cross-domain requests from any domain (domain='*' or no domain restrictions).
A system is affected if it runs RSA Archer version 4.3, 4.5, 5.0, 5.1, or 5.2 (pre-SP1) AND contains permissive cross-domain policy files that allow unrestricted Silverlight cross-origin access.
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 dataUpgrade RSA Archer GRC to version 5.2SP1 or later. Additionally, review and properly configure the clientaccesspolicy.xml and crossdomain.xml files to enforce strict cross-origin restrictions for Silverlight clients.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.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,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-2292 — 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-2292 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