Data Center Network ManagerApplication · Cisco

CVE-2021-1269

MEDIUM · 6.3 CVSS v3.1 Published 2021-01-20
Fix available
A fix is available. Upgrade to 11.5 or later.
See remediation →
69/100
Remediation priority · Elevated
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 web-based management interface of Cisco Data Center Network Manager (DCNM) could allow an authenticated, remote attacker to view, modify, and delete data without proper authorization. For more information about these vulnerabilities, see the Details section of this advisory.

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 authorization flaws in Cisco DCNM's web-based management interface allow authenticated users to bypass proper authorization checks and perform unauthorized read, write, and delete operations on data. These are broken access control vulnerabilities (likely IDOR or privilege escalation) in the web API layer.

MitigationApply the Cisco patch or upgrade to a fixed DCNM version as specified in the Cisco security advisory. Verify that proper authorization checks are enforced post-patch.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

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 Cisco DCNM installation
    Locate the Cisco Data Center Network Manager installation in your environment - this is a Java-based application typically deployed on Windows or Linux servers with a web interface on port 8443 or similar.
    Affected if You find a running instance of Cisco DCNM in your environment
  2. Determine the installed DCNM version
    Access the DCNM web interface and navigate to the About or Help section to view the software version, or use the command line interface if available to query the installed version.
    Affected if The displayed version is lower than 11.5(1)
  3. Confirm web-based management interface is enabled
    Verify that the DCNM web-based management interface is accessible and active - this is the attack surface for CVE-2021-1269.
    Affected if The web management interface is accessible and running
  4. Check for unauthorized access indicators
    Review DCNM audit logs, access logs, or security event logs for any suspicious API calls, privilege escalation attempts, or unauthorized data access from authenticated users.
    Affected if You find evidence of authenticated users accessing data or functions outside their authorized scope

Your environment is affected if the installed Cisco DCNM version is below 11.5(1) and the web-based management interface is enabled and accessible to authenticated users.

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 Cisco patch or upgrade to a fixed DCNM version as specified in the Cisco security advisory. Verify that proper authorization checks are enforced post-patch.

Fix this in Data Center Network Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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