CVE-2017-8004
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 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) allow an application administrator to upload arbitrary files that may potentially contain a malicious code. The malicious file could be then executed on the affected system with the privileges of the user the application is running under.
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 confidenceArbitrary file upload vulnerability in RSA Identity Governance and Lifecycle, RSA Via Lifecycle and Governance, and RSA IMG allows application administrators to upload files containing malicious code that can be executed with the privileges of the application service account.
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.0.1= 7.0.1.1= 7.0.1.2= 7.0.1.3= 7.0.2= 7.0.2.1= 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= 7.0= 7.0.0.1= 7.0.0.2= 7.0.0.3= 7.0.0.4= 7.0.0.5CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
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 product and versionLocate the RSA application installation directory and check version files or use the product's admin interface to view the version information. Common locations include /opt/rsa or installation-specific directories. The product may display its version in the About section of the administrative console.Affected if The installed version matches any version listed in the affected products list (7.0.1, 7.0.1.1, 7.0.1.2, 7.0.1.3, 7.0.2, 7.0.2.1, 6.9.1 through 6.9.1.11, or 7.0 through 7.0.0.5).
-
Verify application administrator access existsReview user accounts with administrator privileges in the RSA application. Log into the administrative console and navigate to the user management section to enumerate accounts with upload privileges.Affected if Any administrator-level account exists in the system and the version is vulnerable.
-
Inspect upload directories for unexpected filesExamine the file upload directories used by the RSA application. Common upload paths may be found in application configuration files. Look for files with extensions such as .jsp, .php, .exe, or .sh that were not explicitly uploaded by legitimate administrators.Affected if Suspicious executable files are present in upload directories and the application version is in the affected list.
A user is affected if the RSA Identity Governance and Lifecycle, RSA Identity Management and Governance, or RSA Via Lifecycle and Governance installation matches any of the specific versions listed and the application service is running with administrator-accessible upload functionality.
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-supplied patches for affected versions (7.0.1, 7.0.2, 7.0, 6.9.1). Until patched, strictly limit application administrator access, monitor upload directories, and consider network isolation of the affected systems.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-8004 — 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-2017-8004 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