CVE-2017-8002
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 · uneditedEMC Data Protection Advisor prior to 6.4 contains multiple blind SQL injection vulnerabilities. A remote authenticated attacker may potentially exploit these vulnerabilities to gain information about the application by causing execution of arbitrary SQL commands.
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 confidenceEMC Data Protection Advisor versions prior to 6.4 contain multiple blind SQL injection vulnerabilities. An attacker with valid authentication credentials can exploit these vulnerabilities to inject and execute arbitrary SQL commands through the application, potentially exposing sensitive database information or escalating privileges within the database.
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<= 6.3CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/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 if EMC Data Protection Advisor is installedCheck for the DPA application through system services, installed programs list, or common installation directories such as C:\Program Files\EMC\Data Protection Advisor or /opt/emc/dpa on Linux systemsAffected if The product is not found on the system, meaning the CVE does not apply
-
Determine the installed DPA versionLocate the DPA version information through the application web interface (typically at /dpaua/about or in the Help > About section), check the installed software package version, or query the DPA service informationAffected if The installed version is 6.3 or earlier (any version prior to 6.4)
-
Verify the application web interface accessibilityCheck if the DPA web interface port (default 9002 or 8443) is listening and accessible on the server or networkAffected if The web interface is exposed without proper access controls, increasing exposure to authenticated attackers
-
Confirm authentication is required for the web interfaceReview the DPA configuration to verify that user authentication is enabled and required for accessing the applicationAffected if The application allows unauthenticated access, which would actually be a different (more severe) issue but could also mean the SQL injection is reachable without credentials
-
Check for recent security updates or patchesReview the DPA patch history or release notes to confirm whether version 6.4 or later patches have been appliedAffected if The system has not been updated to version 6.4 or later and remains on a vulnerable version
A user is affected if EMC Data Protection Advisor is installed and the version is 6.3 or earlier, as the blind SQL injection vulnerabilities exist in versions prior to 6.4.
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 EMC Data Protection Advisor to version 6.4 or later. Additionally, implement parameterized queries or prepared statements across all database interaction points to prevent SQL injection, and conduct input validation audits on all user-supplied data fields.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.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 $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-8002 — 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-8002 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