Data Center Network ManagerApplication · Cisco

CVE-2019-15982

HIGH · 7.2 CVSS v3.1 Published 2020-01-06
Fix available
A fix is available. Upgrade to 11.3 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
Multiple vulnerabilities in the REST and SOAP API endpoints and the Application Framework feature of Cisco Data Center Network Manager (DCNM) could allow an authenticated, remote attacker to conduct directory traversal attacks on an affected device. To exploit these vulnerabilities, an attacker would need administrative privileges on the DCNM application. For more information about these vulnerabilities, see the Details section of this advisory. Note: The severity of these vulnerabilities is aggravated by the vulnerabilities described in the Cisco Data Center Network Manager Authentication Bypass Vulnerabilities advisory, published simultaneously with this one.

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 confidence

Multiple directory traversal vulnerabilities exist in the REST and SOAP API endpoints and Application Framework feature of Cisco DCNM. An attacker with administrative credentials can manipulate path traversal sequences in API requests to access files outside the web root directory, potentially reading sensitive system files or configuration data.

MitigationApply the relevant Cisco patches for DCNM per the advisory. Restrict administrative access to trusted personnel and consider network segmentation to limit exposure of the DCNM management interface.

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
Data Center Network ManagerApplication
Affected:< 11.3\(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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Cisco DCNM is present
    Locate the DCNM installation directory or check running services for Cisco Data Center Network Manager processes
    Affected if DCNM software is installed on the system
  2. Determine installed DCNM version
    Check the DCNM version through the web interface, command line, or installation metadata and compare to the affected range (versions prior to 11.3(1))
    Affected if Installed version is lower than 11.3(1)
  3. Verify REST API endpoint accessibility
    Attempt to access the REST API endpoint (typically at /rest/ or /api/ path) or check DCNM configuration for REST API enablement status
    Affected if REST API endpoint is exposed and accessible
  4. Verify SOAP API endpoint accessibility
    Attempt to access the SOAP API endpoint or check DCNM configuration for SOAP API service status
    Affected if SOAP API endpoint is exposed and accessible
  5. Confirm Application Framework feature status
    Check DCNM configuration or feature list to determine if the Application Framework is enabled
    Affected if Application Framework feature is enabled in DCNM

Environment is affected if Cisco DCNM version is below 11.3(1) and either the REST/SOAP API or Application Framework is accessible with administrative credentials.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 11.3 or later
Fixed in 11.3
Interim mitigation

Apply the relevant Cisco patches for DCNM per the advisory. Restrict administrative access to trusted personnel and consider network segmentation to limit exposure of the DCNM management interface.

Fix this in Data Center Network Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-15982 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-15982 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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