Network Services OrchestratorApplication · Cisco

CVE-2021-1132

HIGH · 7.5 CVSS v3.1 Published 2024-11-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
A vulnerability in the API subsystem and in the web-management interface of Cisco Network Services Orchestrator (NSO) could allow an unauthenticated, remote attacker to access sensitive data. This vulnerability exists because the web-management interface and certain HTTP-based APIs do not properly validate user-supplied input. An attacker could exploit this vulnerability by sending a crafted HTTP request that contains directory traversal character sequences to an affected system. A successful exploit could allow the attacker to access sensitive files on the affected system.Cisco has released software updates that address this vulnerability. There are no workarounds that address this vulnerability.

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

A directory traversal vulnerability in Cisco NSO's web-management interface and HTTP-based APIs allows unauthenticated remote attackers to access sensitive files by sending crafted HTTP requests containing traversal sequences (e.g., ../). The vulnerability stems from improper validation of user-supplied input.

MitigationApply the Cisco-provided software update to a patched version of NSO. No workarounds exist; upgrading is the only remediation path.

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
Network Services OrchestratorApplication
Affected:= 5.3.1= 5.4= 5.4.0.1= 5.4.0.2

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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checks

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

  1. Confirm Cisco NSO installation and version
    Run 'ncs --version' from the command line or check the NSO installation directory for version information
    Affected if The installed version matches 5.3.1, 5.4, 5.4.0.1, or 5.4.0.2
  2. Identify exposed web management interface
    Check if the NSO web UI (typically on port 8080 or 8443) is listening on network interfaces accessible to remote attackers using 'netstat -tulpn | grep -E "(8080|8443)"'
    Affected if The web management port is bound to a non-localhost address or is externally accessible
  3. Verify HTTP-based API exposure
    Check if NSO RESTCONF or other HTTP APIs are enabled and exposed by reviewing NSO configuration in $NCS_DIR/etc/ncs/ncs.conf or running 'ncs --status'
    Affected if HTTP-based APIs are enabled and accessible from untrusted networks
  4. Review access controls on NSO interfaces
    Inspect firewall rules or network ACLs protecting NSO management interfaces to determine if unauthenticated access is possible from external IP addresses
    Affected if No authentication or IP-based restrictions are in place for the management interfaces

The environment is affected if Cisco NSO version 5.3.1, 5.4, 5.4.0.1, or 5.4.0.2 is installed AND the web management interface or HTTP-based APIs are accessible to unauthenticated 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Cisco-provided software update to a patched version of NSO. No workarounds exist; upgrading is the only remediation path.

Fix this in Network Services Orchestrator Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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