dbcve.org
Sd WanApplication · Arubanetworks

CVE-2023-22750

CRITICAL · 9.8 CVSS v3.1 Published 2023-03-01
Fix available
A fix is available. Upgrade to after 10.3.1.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 multiple command injection vulnerabilities that could lead to unauthenticated remote code execution by sending specially crafted packets destined to the PAPI (Aruba Networks 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 command injection vulnerabilities exist in the PAPI (Aruba Networks access point management protocol) implementation. Attackers can send specially crafted UDP packets to port 8211 to achieve unauthenticated remote code execution with privileged (root) system privileges.

MitigationApply vendor-supplied patches or firmware updates from Aruba Networks to address the command injection vulnerabilities in the PAPI protocol. If patching is not immediately possible, consider network segmentation to restrict access to UDP port 8211.

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
Sd WanApplication
Affected:>= 8.7.0.0-2.3.0.0, <= 8.7.0.0-2.3.0.8
ArubaosOperating system
Affected:>= 8.6.0.0, <= 8.6.0.19>= 8.10.0.0, <= 8.10.0.4>= 10.3.0.0, <= 10.3.1.0

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 product and firmware version
    Log into the device CLI or web interface and retrieve the system version. For CLI, typically use 'show version' or 'show system info' commands.
    Affected if The product is Aruba Networks SD-WAN or ArubaOS and the version falls within: SD-WAN 8.7.0.0-2.3.0.0 through 8.7.0.0-2.3.0.8; ArubaOS 8.6.0.0 through 8.6.0.19, 8.10.0.0 through 8.10.0.4, or 10.3.0.0 through 10.3.1.0
  2. Verify PAPI service is running on UDP port 8211
    Check if the PAPI protocol service is enabled and listening on UDP port 8211. In CLI, use 'show ip interface' or check the service status. From an external perspective, scan UDP port 8211 using 'nmap -sU -p 8211 <target>'
    Affected if UDP port 8211 is open and responding, indicating PAPI is active on the device
  3. Confirm network exposure to UDP port 8211
    Review firewall rules, ACLs, and network segmentation to determine if UDP port 8211 is reachable from untrusted networks. Check if the management interface is directly exposed to the internet or accessible from less-trusted network segments.
    Affected if UDP port 8211 is accessible from outside the trusted management network or from non-AP devices

You are affected if your device runs an affected ArubaOS or SD-WAN version AND the PAPI service on UDP port 8211 is enabled AND the port is network-accessible from an untrusted source.

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 a release after 10.3.1.0
Interim mitigation

Apply vendor-supplied patches or firmware updates from Aruba Networks to address the command injection vulnerabilities in the PAPI protocol. If patching is not immediately possible, consider network segmentation to restrict access to UDP port 8211.

Recommended fix Moderate confidence

ArubaOS: 8.7.0.0-2.3.1.0 or later (SD-WAN/Controller); ArubaOS 8.6.0.20 or later, 8.10.0.5 or later, 10.3.2.0 or later

  1. 1. Identify the exact Aruba product and version currently installed using 'show version' or through the WebUI.
  2. 2. For ArubaOS (SD-WAN/Controller): Upgrade to version 8.7.0.0-2.3.1.0 or later. For SD-WAN appliances: Upgrade to version 8.7.0.0-2.3.1.0 or later.
  3. 3. Download the appropriate upgrade image from the Aruba Support Portal (https://asp.arubanetworks.com/).
  4. 4. Follow Aruba's standard upgrade procedure: upload the new image via WebUI or CLI, then reboot the device.
  5. 5. After upgrade, verify the version is correct and confirm the vulnerability is patched.
  6. 6. Ensure PAPI UDP port 8211 is not exposed to untrusted networks as a defense-in-depth measure.
Caveat Review Aruba upgrade release notes for potential compatibility issues with existing network configurations and ensure proper backup before upgrading

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

Fix this in Sd Wan Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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