dbcve.org
ArubaosOperating system · Hp

CVE-2023-22782

CRITICAL · 9.8 CVSS v3.1 Published 2023-05-08
Fix available
A fix is available. Upgrade to 8.6.0.0 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
There 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 confidence

Multiple buffer overflow vulnerabilities exist in the PAPI (Aruba Access Point Management Protocol) service listening on UDP port 8211. An unauthenticated attacker can send specially crafted packets to trigger the overflow, achieving arbitrary code execution as a privileged (root) user on the underlying operating system.

MitigationApply available vendor patches for CVE-2023-22782; if no patch is available, restrict network access to UDP port 8211 via firewall or network segmentation to prevent unauthenticated attackers from reaching the PAPI service.

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
ArubaosOperating system
Affected:>= 10.3.0.0, <= 10.3.1.0
InstantosOperating system
Affected:>= 6.4.0.0, <= 6.4.4.8-4.2.4.20>= 6.5.0.0, <= 6.5.4.23>= 8.4.0.0, < 8.6.0.0>= 8.6.0.0, <= 8.6.0.19>= 8.7.0.0, <= 8.9.0.0>= 8.10.0.0, <= 8.10.0.4

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device OS and version
    Run 'show version' on the Aruba controller or access point CLI to obtain the OS name (ArubaOS or InstantOS) and exact version number
    Affected if The version falls within any of the listed affected ranges (ArubaOS 10.3.0.0-10.3.1.0, or InstantOS 6.4.x, 6.5.x, 8.4.x, 8.6.x, 8.7.x-8.9.x, or 8.10.0.0-8.10.0.4)
  2. Verify PAPI service is running on UDP port 8211
    Execute 'show ip udp' or 'show listening-ports' on the CLI to confirm the PAPI service is bound to UDP port 8211
    Affected if The PAPI service is listening on UDP port 8211 and the OS version is in the affected range
  3. Check if UDP port 8211 is exposed to untrusted networks
    Review firewall rules or access lists with 'show ip access-list' and check network interface configurations to determine if UDP port 8211 is reachable from outside the trusted management network
    Affected if UDP port 8211 is accessible from untrusted or external networks without proper filtering
  4. Confirm management interface configuration
    Run 'show interface' and 'show ip interface' to identify which interfaces have the PAPI service bound and their IP addressing
    Affected if The management or production interfaces with PAPI are not isolated by VLANs or network segmentation from untrusted traffic

You are affected if your Aruba device runs ArubaOS 10.3.x or InstantOS 6.4.x-8.10.x within the specified ranges AND the PAPI service on UDP port 8211 is accessible to unauthenticated network attackers.

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.

From vendor data
Upgrade available Upgrade to 8.6.0.0 or later
Fixed in 8.6.0.0
Interim mitigation

Apply available vendor patches for CVE-2023-22782; if no patch is available, restrict network access to UDP port 8211 via firewall or network segmentation to prevent unauthenticated attackers from reaching the PAPI service.

Fix this in Arubaos Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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