dbcve.org
Sd WanApplication · Arubanetworks

CVE-2023-22748

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) running on UDP port 8211. Attackers can send specially crafted packets to achieve unauthenticated remote code execution as a privileged user on the underlying operating system.

MitigationRestrict access to UDP port 8211 at network perimeter, and apply vendor patches to affected Aruba access point devices as soon as possible.

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. Verify UDP port 8211 is exposed
    Scan your network or check listening services on the device using 'netstat -anu | grep 8211' or 'ss -uan | grep 8211' to confirm PAPI is listening
    Affected if UDP port 8211 is open and accessible from untrusted networks
  2. Identify installed ArubaOS version
    On the Aruba device, run 'show version' or check the system info via CLI to retrieve the exact firmware version installed
    Affected if Version matches >= 8.6.0.0 to <= 8.6.0.19, OR >= 8.10.0.0 to <= 8.10.0.4, OR >= 10.3.0.0 to <= 10.3.1.0
  3. Identify installed SD-WAN version
    For Aruba SD-WAN devices, run 'show version' or check the management interface for the firmware build number
    Affected if Version matches >= 8.7.0.0-2.3.0.0 through <= 8.7.0.0-2.3.0.8
  4. Confirm PAPI service is enabled
    Verify the PAPI protocol is active on the device by checking running services or configuration with 'show papi status' or equivalent command for your device
    Affected if PAPI service is enabled and running on UDP port 8211

You are affected if UDP port 8211 is exposed and your device runs a version within the affected ranges for ArubaOS or SD-WAN with PAPI enabled.

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

Restrict access to UDP port 8211 at network perimeter, and apply vendor patches to affected Aruba access point devices as soon as possible.

Recommended fix Moderate confidence

ArubaOS: 8.6.0.20+ / 8.10.0.5+ / 10.3.2.0+; SD-WAN: 8.7.0.0-2.3.0.9+

  1. 1. Identify the exact Aruba product and version currently running using 'show version' or via the WebUI
  2. 2. For ArubaOS: Upgrade to version 8.6.0.20 or later for the 8.6.x branch, version 8.10.0.5 or later for the 8.10.x branch, or version 10.3.2.0 or later for the 10.3.x branch
  3. 3. For SD-WAN: Upgrade to version 8.7.0.0-2.3.0.9 or later
  4. 4. If immediate upgrade is not possible, consider restricting access to UDP port 8211 (PAPI) at the network perimeter to prevent unauthenticated packets from reaching the device
  5. 5. After upgrade, verify the new version is running and review system logs for any signs of exploitation attempts
Caveat Review Aruba release notes for your specific model for any configuration or behavioral changes between versions before upgrading

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

Fix this in Sd Wan Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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