CVE-2017-12346
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 · uneditedMultiple vulnerabilities in Cisco Data Center Network Manager (DCNM) Software could allow a remote attacker to inject arbitrary values into DCNM configuration parameters, redirect a user to a malicious website, inject malicious content into a DCNM client interface, or conduct a cross-site scripting (XSS) attack against a user of the affected software. Cisco Bug IDs: CSCvf40477, CSCvf63150, CSCvf68218, CSCvf68235, CSCvf68247.
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 confidenceMultiple web vulnerabilities in Cisco Data Center Network Manager (DCNM) allow remote attackers to inject arbitrary values into configuration parameters, redirect users to malicious sites, inject malicious content into the client interface, and conduct cross-site scripting (XSS) attacks against users.
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= 10.2\(1\)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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/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.
-
Confirm Cisco DCNM installationIdentify if Cisco Data Center Network Manager is installed on the system. Check for DCNM installation directories, services, or running processes related to 'dcnm' or 'Data Center Network Manager'.Affected if DCNM is not installed on the system, the user is not affected by this CVE.
-
Verify DCNM versionDetermine the installed version of Cisco DCNM. Check the application's about page, installation directory for version files, or use the DCNM CLI/tool with commands like 'dcnm -v' or similar version inquiry commands if available.Affected if The installed version is exactly 10.2(1) - other versions may have different risk levels.
-
Check web interface exposureDetermine if the DCNM web interface is accessible. Identify if the DCNM web server (typically on ports 80, 443, or 8080) is running and exposed to network access.Affected if The DCNM web interface is accessible - these are web-based vulnerabilities requiring user interaction with the web interface.
-
Inspect web logs for injection attemptsReview DCNM web server logs for suspicious parameters, unexpected redirects, or XSS payloads in request URLs, form submissions, or query strings.Affected if Logs contain evidence of injection attempts, malicious redirects, or XSS payloads targeting DCNM web endpoints.
A user is affected only if Cisco DCNM version 10.2(1) is installed and its web interface is accessible; other versions or non-installed states indicate no impact from this specific CVE.
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 Cisco patches for DCNM (Cisco Bug IDs CSCvf40477, CSCvf63150, CSCvf68218, CSCvf68235, CSCvf68247) or implement input validation and output encoding controls; also deploy web application firewall rules to block injection/XSS attempts.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-12346 — 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-12346 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