dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2024-22054

HIGH · 7.5 CVSS v3.1 Published 2024-02-20
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 malformed discovery packet sent by a malicious actor with preexisting access to the network could interrupt the functionality of device management and discovery. Affected Products: UniFi Access Points UniFi Switches UniFi LTE Backup UniFi Express (Only Mesh Mode, Router mode is not affected) Mitigation: Update UniFi Access Points to Version 6.6.55 or later. Update UniFi Switches to Version 6.6.61 or later. Update UniFi LTE Backup to Version 6.6.57 or later. Update UniFi Express to Version 3.2.5 or later.

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 denial-of-service vulnerability exists in UniFi network devices where a malformed discovery packet sent by a malicious actor with preexisting network access can interrupt device management and discovery functionality. The attack exploits the discovery protocol used by UniFi devices to enumerate and manage network infrastructure.

MitigationUpdate affected UniFi devices to the specified firmware versions: Access Points to 6.6.55+, Switches to 6.6.61+, LTE Backup to 6.6.57+, and UniFi Express (Mesh Mode) to 3.2.5+. Network segmentation and access controls should be reviewed to limit exposure to malicious actors.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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 UniFi device type
    Determine if the device is a UniFi Access Point, Switch, LTE Backup, or UniFi Express. Check the device model via the UniFi Controller, device label, or web interface.
    Affected if Device is a UniFi Access Point, Switch, LTE Backup, or UniFi Express running vulnerable firmware
  2. Check installed firmware version
    Access the UniFi Controller or device web interface and locate the firmware version. For Access Points look for version below 6.6.55, for Switches below 6.6.61, for LTE Backup below 6.6.57, and for UniFi Express (Mesh Mode) below 3.2.5.
    Affected if Firmware version is lower than the fixed version for your device type (AP: <6.6.55, Switch: <6.6.61, LTE: <6.6.57, Express: <3.2.5)
  3. Verify discovery protocol is enabled
    Check if the UniFi discovery protocol is active on the device or network segment. This is typically enabled by default for device enumeration. Inspect network settings or controller discovery settings.
    Affected if Discovery protocol is enabled and reachable on the network segment
  4. Assess network access exposure
    Review network segmentation and access controls to determine if an untrusted actor could send packets to the discovery service. The vulnerability requires preexisting network access.
    Affected if Untrusted devices or users can reach the discovery protocol on the UniFi device

You are affected if you run a UniFi device (AP, Switch, LTE Backup, or Express) with firmware below the fixed versions and the discovery protocol is accessible to a malicious actor on your network.

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

Update affected UniFi devices to the specified firmware versions: Access Points to 6.6.55+, Switches to 6.6.61+, LTE Backup to 6.6.57+, and UniFi Express (Mesh Mode) to 3.2.5+. Network segmentation and access controls should be reviewed to limit exposure to malicious actors.

Recommended fix High confidence

UniFi Access Points: 6.6.55+ | Switches: 6.6.61+ | LTE Backup: 6.6.57+ | Express Mesh: 3.2.5+

  1. Identify all affected UniFi devices on the network (Access Points, Switches, LTE Backup, and Express devices in Mesh Mode)
  2. For UniFi Access Points: Upgrade firmware to version 6.6.55 or later via the UniFi Controller
  3. For UniFi Switches: Upgrade firmware to version 6.6.61 or later via the UniFi Controller
  4. For UniFi LTE Backup: Upgrade firmware to version 6.6.57 or later via the UniFi Controller
  5. For UniFi Express: Only upgrade devices running in Mesh Mode to version 3.2.5 or later (Router mode is not affected)
  6. Verify all devices are running the patched firmware versions after upgrade
Caveat UniFi Express: Only Mesh Mode is affected; Router mode does not require updating

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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