Data Center Network ManagerApplication · Cisco

CVE-2021-1272

HIGH · 8.8 CVSS v3.1 Published 2021-01-20
Fix available
A fix is available. Upgrade to 11.5 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
A vulnerability in the session validation feature of Cisco Data Center Network Manager (DCNM) could allow an unauthenticated, remote attacker to bypass access controls and conduct a server-side request forgery (SSRF) attack on a targeted system. This vulnerability is due to insufficient validation of parameters in a specific HTTP request by an attacker. An attacker could exploit this vulnerability by sending a crafted HTTP request to an authenticated user of the DCNM web application. A successful exploit could allow the attacker to bypass access controls and gain unauthorized access to the Device Manager application, which provides access to network devices managed by the system.

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

This vulnerability in Cisco DCNM's session validation feature allows an unauthenticated remote attacker to bypass access controls by sending a crafted HTTP request with insufficiently validated parameters, enabling server-side request forgery (SSRF) and unauthorized access to the Device Manager application.

MitigationApply the vendor patch from Cisco for DCNM. If immediate patching is not possible, restrict network access to the DCNM management interfaces and monitor for suspicious HTTP requests.

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.5\(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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 the installed DCNM version
    Log into the DCNM web interface and navigate to the About or Administration page, or run 'show version' via CLI if you have appliance access, to retrieve the exact software version number
    Affected if The version displayed is below 11.5(1)
  2. Verify the DCNM web management interface is accessible
    Confirm that the DCNM web interface (typically ports 80/443 or the Device Manager application) is reachable on the network
    Affected if The management interface is exposed and responds to HTTP/HTTPS requests
  3. Check for active session validation on HTTP endpoints
    Review DCNM configuration for session validation settings, typically found in the web server or security settings section of the administration console
    Affected if Session validation is enabled but the version is unpatched
  4. Confirm Device Manager application accessibility
    Attempt to access the Device Manager application component via its URL path (such as /dm or similar web endpoint) without authentication
    Affected if The application is reachable and responds without proper authentication

If the installed Cisco DCNM version is below 11.5(1) and the web-based management or Device Manager interface is network-accessible, the environment is affected by this vulnerability.

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.5 or later
Fixed in 11.5
Interim mitigation

Apply the vendor patch from Cisco for DCNM. If immediate patching is not possible, restrict network access to the DCNM management interfaces and monitor for suspicious HTTP requests.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-1272 — 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-2021-1272 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