CVE-2024-54750
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 · uneditedUbiquiti U6-LR 6.6.65 was discovered to contain a hardcoded password vulnerability in /etc/shadow, which allows attackers to log in as root. NOTE: In Ubiquiti's view there is no vulnerability as the Hardcoded Password should be after setup not before.
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 · moderate confidenceThe Ubiquiti U6-LR access point firmware version 6.6.65 contains a hardcoded password stored in /etc/shadow, enabling unauthenticated attackers to obtain root shell access to the device. This is a pre-authentication vulnerability allowing remote root compromise.
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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Ubiquiti U6-LR devices in your environmentLocate all wireless access points and filter for Ubiquiti U6-LR models. Check your network inventory, device onboarding records, or use network discovery tools to enumerate access points.Affected if You have Ubiquiti U6-LR access points deployed in your network.
-
Check the firmware version on U6-LR devicesAccess the UniFi Controller or the device's web interface. Navigate to the device settings or use the controller's device list to view the firmware version column. Alternatively, SSH to the device and run: cat /etc/version or ubnt-sysinfo.Affected if The firmware version reported is exactly 6.6.65.
-
Compare against the affected version rangeVerify if the installed version matches 6.6.65. The vulnerability is specific to this version according to the CVE summary.Affected if The device firmware version is 6.6.65.
-
Inspect /etc/shadow for the hardcoded passwordIf you have SSH access to the device, examine /etc/shadow for the root account entry. A hardcoded password hash will be present even if you have changed the admin password through normal management interfaces. The presence of a fixed hash indicates the vulnerability.Affected if The root account in /etc/shadow contains a password hash that persists regardless of management interface password changes.
You are affected if you have Ubiquiti U6-LR access points running firmware version 6.6.65, which contains a hardcoded root password in /etc/shadow enabling unauthenticated remote root access.
Generated from the published advisory. Verify against your own configuration.
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 dataSince Ubiquiti does not consider this a vulnerability requiring a patch, mitigate by isolating the device behind a firewall restricting management access, monitoring for unauthorized access attempts, and contacting Ubiquiti for an official firmware remediation.
- Consultation6.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,816.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-54750 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-54750 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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