CVE-2016-6647
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 · uneditedCross-site scripting (XSS) vulnerability in EMC ViPR SRM before 4.0.1 allows remote authenticated users to inject arbitrary web script or HTML 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 · high confidenceCross-site scripting (XSS) vulnerability in EMC ViPR SRM prior to version 4.0.1 allows authenticated users to inject arbitrary web script or HTML through unspecified input vectors. This is a stored XSS issue where malicious scripts are persisted in the application and executed when other users view the affected content.
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.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed ViPR SRM versionAccess the ViPR SRM admin console or use the product's built-in about/version information page. Typically found under Help > About or System > Administration > General in the web interface. Alternatively, check the installation directory for version files or use the CLI command 'viprsradm --version' if available.Affected if The installed version is 4.0 or earlier (any version <= 4.0 indicates vulnerability)
-
Confirm ViPR SRM service is runningVerify the ViPR SRM application is accessible by attempting to reach the web interface URL (typically https://<hostname>/viprsrm or similar). Check if the login page loads successfully.Affected if The application is running and accessible, combined with a vulnerable version (< 4.0.1)
-
Verify authentication mechanism is enabledCheck if user authentication is enabled in ViPR SRM. This can be done through the admin console under Security or User Management settings. Determine if local user accounts or external authentication (LDAP/Active Directory) is configured.Affected if User authentication is enabled and active - this is required for the authenticated XSS to be exploitable
-
Identify if user-supplied input fields existReview the ViPR SRM interface for fields that accept and store user input such as device names, descriptions, custom labels, report names, or dashboard widgets. These are potential vectors for stored XSS.Affected if The application stores user-supplied data and displays it to other users - this is necessary for the stored XSS to execute
A user is affected if they are running ViPR SRM version 4.0 or earlier AND the application is accessible with authenticated user accounts, as the vulnerability requires an authenticated user to inject malicious scripts that persist and execute when viewed by other users.
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 to EMC ViPR SRM version 4.0.1 or later. Additionally, implement robust input validation and output encoding for all user-supplied data to prevent XSS attacks.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-6647 — 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-2016-6647 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