CVE-2017-8004
No exploitation reported by the sources we read.
- Published2017-07-17
- WeaknessCWE-20
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
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) 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.
Timeline
dates in UTC- 2017-07-1714:29CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 18:48 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2017-8004?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2017-8004?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 6.9 | = 6.9.1 | no fix published | NVD |
| 6.9 | = 6.9.1.1 | no fix published | NVD |
| 6.9 | = 6.9.1.2 | no fix published | NVD |
| 6.9 | = 6.9.1.3 | no fix published | NVD |
| 6.9 | = 6.9.1.4 | no fix published | NVD |
| 6.9 | = 6.9.1.5 | no fix published | NVD |
| 6.9 | = 6.9.1.6 | no fix published | NVD |
| 6.9 | = 6.9.1.7 | no fix published | NVD |
| 6.9 | = 6.9.1.8 | no fix published | NVD |
| 6.9 | = 6.9.1.9 | no fix published | NVD |
| 6.9 | = 6.9.1.10 | no fix published | NVD |
| 6.9 | = 6.9.1.11 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 7.0 | = 7.0.1 | no fix published | NVD |
| 7.0 | = 7.0.1.1 | no fix published | NVD |
| 7.0 | = 7.0.1.2 | no fix published | NVD |
| 7.0 | = 7.0.1.3 | no fix published | NVD |
| 7.0 | = 7.0.2 | no fix published | NVD |
| 7.0 | = 7.0.2.1 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 7.0 | = 7.0 | no fix published | NVD |
| 7.0 | = 7.0.0.1 | no fix published | NVD |
| 7.0 | = 7.0.0.2 | no fix published | NVD |
| 7.0 | = 7.0.0.3 | no fix published | NVD |
| 7.0 | = 7.0.0.4 | no fix published | NVD |
| 7.0 | = 7.0.0.5 | no fix published | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
No fix published by the sources we read yet. NVD record
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
- NVDCVSS 3.07.2read 2026-10-23
- NVDCVSS 2.06.5read 2026-10-23
- NVDweakness (CWE)CWE-20read 2026-10-23
- FIRST EPSSEPSS score2.2 %2026-10-22
Technical details
- CVSS v3 Vector
- CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
- Published
- 2017-07-17
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2017-8004?
Is CVE-2017-8004 actively exploited?
What is the CVSS score for CVE-2017-8004?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.