dbcve.org
Rsa Identity Governance And LifecycleApplication · Emc

CVE-2017-8005

MEDIUM · 5.4 CVSS v3.0 Published 2017-07-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
The EMC RSA Identity Governance and Lifecycle, RSA Via Lifecycle and Governance, and RSA IMG products (RSA Identity Governance and Lifecycle versions 7.0.1, 7.0.2, all patch levels; RSA Via Lifecycle and Governance version 7.0, all patch levels; RSA Identity Management and Governance (RSA IMG) versions 6.9.1, all patch levels) are affected by multiple stored cross-site scripting vulnerabilities. Remote authenticated malicious users could potentially inject arbitrary HTML code to the application.

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 confidence

This is a stored (persistent) cross-site scripting vulnerability in RSA Identity Governance and Lifecycle, RSA Via Lifecycle and Governance, and RSA IMG products. Authenticated malicious users can inject arbitrary HTML/JavaScript code that gets permanently stored in the application and executes when other users access the affected pages.

MitigationApply vendor-supplied patches for the affected versions and implement output encoding/sanitization for user-supplied input in the application.

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
Rsa Identity Governance And LifecycleApplication
Affected:= 7.0.1= 7.0.1.1= 7.0.1.2= 7.0.1.3= 7.0.2= 7.0.2.1
Rsa Identity Management And GovernanceApplication
Affected:= 6.9.1= 6.9.1.1= 6.9.1.2= 6.9.1.3= 6.9.1.4= 6.9.1.5= 6.9.1.6= 6.9.1.7= 6.9.1.8= 6.9.1.9= 6.9.1.10= 6.9.1.11
Rsa Via Lifecycle And GovernanceApplication
Affected:= 7.0= 7.0.0.1= 7.0.0.2= 7.0.0.3= 7.0.0.4= 7.0.0.5

CVSS 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
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed RSA product and version
    Locate the product version through the administrative console, about page, or system information file. For RSA Identity Governance and Lifecycle, this is typically found in the admin UI under System > Settings > System Information, or in the installation directory's version file.
    Affected if The product name matches one of: RSA Identity Governance and Lifecycle, RSA Via Lifecycle and Governance, or RSA IMG, AND the version matches any of the listed affected versions (7.0.1 through 7.0.2.1 for Identity Governance; 6.9.1 through 6.9.1.11 for Identity Management and Governance; 7.0 through
  2. Confirm the web application interface is active
    Verify the RSA web interface is accessible by attempting to reach the application URL (typically https://hostname/aveksa/ or similar). This vulnerability affects web-based stored XSS, so the application must be running.
    Affected if The RSA web application is accessible and accepts authenticated user sessions.
  3. Determine if user authentication is enabled
    Check whether local or remote user authentication (LDAP, AD, etc.) is configured in the Identity Governance/Lifecycle system. This can be verified through the admin console under User Management or Security settings.
    Affected if User authentication is enabled and multiple users have access to the application, as the stored XSS payload would need to be viewed by other users to execute.

A user is affected if they are running any of the specific product versions listed AND the RSA web interface is active with authenticated user access, allowing stored malicious scripts to execute in other users' browsers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied patches for the affected versions and implement output encoding/sanitization for user-supplied input in the application.

Fix this in Rsa Identity Governance And Lifecycle Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-8005 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-8005 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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