CVE-2023-35980
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 · uneditedThere are buffer overflow vulnerabilities in multiple underlying services that could lead to unauthenticated remote code execution by sending specially crafted packets destined to the PAPI (Aruba's access point management protocol) UDP port (8211). Successful exploitation of these vulnerabilities result in the ability to execute arbitrary code as a privileged user on the underlying operating system.
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 confidenceBuffer overflow vulnerabilities in Aruba's PAPI (Access Point Management Protocol) service on UDP port 8211 allow unauthenticated attackers to execute arbitrary code with privileged (root) OS-level access by sending specially crafted UDP packets.
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>= 10.4.0.0, < 10.4.0.2>= 6.4.0.0, < 6.4.4.8-4.2.4.22>= 6.5.0.0, < 6.5.4.25>= 8.6.0.0, < 8.6.0.21>= 8.10.0.0, < 8.10.0.7>= 8.11.0.0, < 8.11.1.1CVSS 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 product and OS versionRun 'show version' or 'show system info' on the Aruba device CLI to determine if it runs ArubaOS or HP InstantOS and note the exact version numberAffected if The device runs ArubaOS or HP InstantOS and the version falls within the affected ranges
-
Compare installed version against CVE-affected rangesFor ArubaOS: verify version is >= 10.4.0.0 but < 10.4.0.2. For HP InstantOS: verify version is >= 6.4.0.0 but < 6.4.4.8-4.2.4.22, OR >= 6.5.0.0 but < 6.5.4.25, OR >= 8.6.0.0 but < 8.6.0.21, OR >= 8.10.0.0 but < 8.10.0.7, OR >= 8.11.0.0 but < 8.11.1.1Affected if The installed version matches any of the specified version ranges
-
Verify UDP port 8211 is listeningRun 'show ip interface' or use 'netstat -anu | grep 8211' (if available) to confirm the PAPI service on UDP port 8211 is enabled and bound to an interfaceAffected if UDP port 8211 is open and listening on any interface accessible to untrusted networks
-
Check network exposure of the PAPI serviceReview firewall rules, ACLs, or network segmentation to determine if UDP port 8211 is accessible from untrusted or external networks. Use 'show ip access-list' (if available) to inspect applied access controlsAffected if UDP port 8211 is reachable from networks outside the trusted management segment
A device is affected if it runs a vulnerable ArubaOS or HP InstantOS version within the specified ranges AND has UDP port 8211 exposed to untrusted network 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.
dbcve · scoped6.4.4.8-4.2.4.226.5.4.258.6.0.21
Apply Aruba's security patches immediately; if patches are unavailable, restrict network access to UDP port 8211 via firewall rules or network segmentation to prevent unauthorized external traffic from reaching affected devices.
ArubaOS 10.4.0.2 or later; InstantOS 6.4.4.8-4.2.4.22 / 6.5.4.25 / 8.6.0.21 / 8.10.0.7 or later depending on branch
- Identify the currently installed ArubaOS or InstantOS version using 'show version' command
- For ArubaOS: Upgrade to version 10.4.0.2 or later by uploading the firmware file via WebUI or CLI (copy flash:<filename> flash: and boot system <file>)
- For InstantOS: Upgrade to the appropriate fixed version based on your current branch: 6.4.x branch to 6.4.4.8-4.2.4.22 or later, 6.5.x branch to 6.5.4.25 or later, 8.6.x branch to 8.6.0.21 or later, 8.10.x branch to 8.10.0.7 or later
- Schedule maintenance window as upgrade requires controller reboot
- After upgrade, verify the fix by checking 'show version' confirms the fixed version is running
- Restrict access to UDP port 8211 (PAPI) from untrusted networks as an additional mitigation if immediate upgrade is not possible
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-35980 — 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-35980 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