CVE-2023-35085
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 · uneditedAn integer overflow vulnerability in all UniFi Access Points and Switches, excluding the Switch Flex Mini, with SNMP Monitoring and default settings enabled could allow a Remote Code Execution (RCE). Affected Products: All UniFi Access Points (Version 6.5.50 and earlier) All UniFi Switches (Version 6.5.32 and earlier) -USW Flex Mini excluded. Mitigation: Update UniFi Access Points to Version 6.5.62 or later. Update the UniFi Switches to Version 6.5.59 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 confidenceAn integer overflow vulnerability in the SNMP monitoring component of UniFi Access Points (versions 6.5.50 and earlier) and UniFi Switches (versions 6.5.32 and earlier, excluding Flex Mini) with default settings enabled allows remote code execution. The vulnerability is triggered via SNMP, indicating improper bounds checking on integer values that can lead to heap or stack corruption enabling RCE.
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<= 6.5.50<= 6.5.32CVSS 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 the UniFi device typeDetermine whether the device is a UniFi Access Point or a UniFi Switch (excluding Flex Mini). This can be done via the UniFi Controller console, device overview, or device label.Affected if Device is a UniFi Access Point or UniFi Switch (non-Flex Mini)
-
Check the installed firmware versionLocate the firmware version in the UniFi Controller under Device > Info, or via CLI using 'info' command for the device. Compare the version number to the affected ranges: <= 6.5.50 for Access Points, <= 6.5.32 for Switches.Affected if Firmware version is 6.5.50 or earlier on UniFi AP, or 6.5.32 or earlier on UniFi Switch
-
Verify SNMP is enabledCheck the SNMP configuration in UniFi Controller under Settings > SNMP, or via device configuration. Confirm whether the SNMP monitoring feature is turned on.Affected if SNMP is enabled on the device
-
Check SNMP community string configurationInspect the SNMP community string settings. Since the vulnerability applies with default settings, verify if the default public/community string is in use or if default SNMP settings have not been modified.Affected if Default SNMP community string or default SNMP settings are in use
The environment is affected if you have a UniFi Access Point on firmware <= 6.5.50 or a UniFi Switch on firmware <= 6.5.32 with SNMP enabled using default configuration settings.
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.
dbcve · scopedUpdate UniFi Access Points to firmware version 6.5.62 or later, and UniFi Switches to version 6.5.59 or later. Alternatively, disable SNMP monitoring if not required, though updating is strongly recommended given the critical severity.
UniFi Access Points: 6.5.62 or later | UniFi Switches: 6.5.59 or later
- Identify all UniFi Access Points running firmware version 6.5.50 or earlier
- Identify all UniFi Switches running firmware version 6.5.32 or earlier (excluding Switch Flex Mini which is not affected)
- Access the UniFi Network Controller or UniFi OS Console
- Navigate to the device management section
- For each affected Access Point, upgrade firmware to version 6.5.62 or later
- For each affected Switch, upgrade firmware to version 6.5.59 or later
- Verify all devices are running the patched firmware versions after update
- Confirm SNMP monitoring functionality is working correctly post-update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-35085 — 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-2023-35085 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