dbcve.org
Nx OsOperating system · Cisco

CVE-2022-20624

HIGH · 7.5 CVSS v3.1 Published 2022-02-23
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 Cisco Fabric Services over IP (CFSoIP) feature of Cisco NX-OS Software could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition on an affected device. This vulnerability is due to insufficient validation of incoming CFSoIP packets. An attacker could exploit this vulnerability by sending crafted CFSoIP packets to an affected device. A successful exploit could allow the attacker to cause the affected device to reload, resulting in a DoS condition.

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 vulnerability in Cisco Fabric Services over IP (CFSoIP) feature of Cisco NX-OS Software allows an unauthenticated remote attacker to send crafted CFSoIP packets to an affected device. Due to insufficient validation of incoming packets, the attacker can trigger a device reload, causing denial of service.

MitigationApply the Cisco NX-OS software update that addresses this vulnerability. If unable to immediately patch, consider restricting network access to CFSoIP ports from untrusted sources using ACLs or firewall rules until the patch can be deployed.

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
Nx OsOperating system
Affected:= 7.0\(3\)= 9.2\(2\)= 9.2\(3\)= 9.3\(3\)= 9.3\(5\)= 4.1\(1a\)a

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 NX-OS version
    Run 'show version' on the device CLI or retrieve the version via SNMP/management interface
    Affected if The displayed version matches any of these exact versions: 7.0(3), 9.2(2), 9.2(3), 9.3(3), 9.3(5), or 4.1(1a)a
  2. Confirm CFSoIP feature is enabled
    Run 'show feature | include fabric' or 'show running-config | include feature fabric' to check if Cisco Fabric Services over IP feature is turned on
    Affected if CFSoIP or fabric services feature shows as 'enabled' in the output
  3. Check CFSoIP port exposure
    Run 'show tcp brief | include 8787' or check ACLs and interface configurations for port 8787 (default CFSoIP port) to see if it is accessible from untrusted networks
    Affected if Port 8787 (or configured CFSoIP port) is open to untrusted/internet-facing networks
  4. Verify CFSoIP configuration
    Run 'show running-config | include cfsoip' or 'show cfsoip' to examine CFSoIP-specific settings and source validation
    Affected if CFSoIP is configured and incoming packet validation appears weak or disabled

You are affected if your device runs NX-OS version 7.0(3), 9.2(2), 9.2(3), 9.3(3), 9.3(5), or 4.1(1a)a AND has the CFSoIP feature enabled with port 8787 exposed to untrusted networks.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Cisco NX-OS software update that addresses this vulnerability. If unable to immediately patch, consider restricting network access to CFSoIP ports from untrusted sources using ACLs or firewall rules until the patch can be deployed.

Recommended fix Moderate confidence

Cisco NX-OS fixed release as specified in the Cisco Security Advisory for CVE-2022-20624 (consult tools.cisco.com for exact version)

  1. 1. Identify the current Cisco NX-OS version running on the affected device using 'show version'
  2. 2. Access Cisco.com and navigate to the Security Advisory for CVE-2022-20624
  3. 3. Download the recommended fixed NX-OS version for your specific platform from the Cisco advisory
  4. 4. Upload the new NX-OS image to the device's bootflash
  5. 5. Configure the device to boot from the new image using 'install all' command
  6. 6. Verify the device reloads with the patched version
  7. 7. Confirm CFSoIP functionality is restored using 'show cfs status'
Caveat Standard NX-OS upgrade considerations apply - verify hardware compatibility and review release notes for any feature changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Nx Os Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,180
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-20624 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2022-20624 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