Ua Lite FirmwareOperating system · Ui

CVE-2022-22570

CRITICAL · 10.0 CVSS v3.1 Published 2022-04-01
Fix available
A fix is available. Upgrade to 3.8.31.13 or later.
See remediation →
100/100
Remediation priority · Urgent
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 buffer overflow vulnerability found in the UniFi Door Access Reader Lite’s (UA Lite) firmware (Version 3.8.28.24 and earlier) allows a malicious actor who has gained access to a network to control all connected UA devices. This vulnerability is fixed in Version 3.8.31.13 and 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

Buffer overflow in UniFi Door Access Reader Lite firmware (versions 3.8.28.24 and earlier) allows a network-adjacent attacker to execute arbitrary code and gain control of connected UA devices. This is a critical firmware vulnerability in physical access control hardware.

MitigationUpdate UA Lite firmware to version 3.8.31.13 or later. Prior to deployment, verify the update in a staging environment to ensure door access functionality remains operational.

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
Ua Lite FirmwareOperating system
Affected:< 3.8.31.13

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 device model
    Check the physical UniFi Door Access Reader Lite device or access its management interface to confirm it is a UA Lite model. This vulnerability only affects the Reader Lite hardware, not other UniFi access devices.
    Affected if Device is not a UniFi Door Access Reader Lite model
  2. Access firmware version information
    Log into the UniFi Door Access Reader Lite management console or access it via the UniFi Network controller. Navigate to the device settings or firmware information section to retrieve the current running firmware version.
    Affected if Unable to retrieve firmware version from device interface
  3. Compare installed version to affected range
    Compare the installed firmware version number to the affected range: versions earlier than 3.8.31.13 (including 3.8.28.24 and all prior versions) are vulnerable. The specific vulnerable versions are < 3.8.31.13.
    Affected if Installed firmware version is earlier than 3.8.31.13 (for example 3.8.28.24, 3.8.20.15, or any version below 3.8.31.13)
  4. Verify network exposure
    Confirm the device is network-adjacent to untrusted networks, as the attack vector requires a network-adjacent attacker. Check network segmentation and ACLs controlling access to the UA Lite device.
    Affected if Device is accessible from untrusted network segments without firewall protection

A system is affected if it is a UniFi Door Access Reader Lite running firmware version earlier than 3.8.31.13.

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
Upgrade available Upgrade to 3.8.31.13 or later
Fixed in 3.8.31.13
Interim mitigation

Update UA Lite firmware to version 3.8.31.13 or later. Prior to deployment, verify the update in a staging environment to ensure door access functionality remains operational.

Recommended fix High confidence

Firmware version 3.8.31.13 or later

  1. Obtain UniFi Door Access Reader Lite firmware version 3.8.31.13 or later from the official Ubiquiti downloads portal
  2. Access the UniFi management console or UA Lite device management interface
  3. Navigate to the device settings for the UA Lite reader
  4. Upload the downloaded firmware file (3.8.31.13 or later) to the device
  5. Apply the firmware update and wait for the device to reboot
  6. Verify the installed firmware version is 3.8.31.13 or higher

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

Fix this in Ua Lite Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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