dbcve.org
Sd WanApplication · Arubanetworks

CVE-2023-22749

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) handling code. By sending specially crafted UDP packets to port 8211, unauthenticated attackers can inject arbitrary OS commands that execute with elevated (privileged) privileges on affected Aruba access point devices.

MitigationApply vendor-provided patches immediately; if patching is not immediately feasible, restrict network access to UDP port 8211 via firewall or ACLs 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
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 Aruba device type
    Determine if the device is an Aruba SD-WAN appliance or an ArubaOS access point. Use 'show version' or check the device model via the management interface.
    Affected if The device is an Aruba SD-WAN or ArubaOS access point.
  2. Check the installed software version
    Run 'show version' on the device CLI or check the firmware version via the web management interface. Compare the version number against the affected ranges: 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.
    Affected if The installed version falls within any of the affected version ranges.
  3. Verify UDP port 8211 accessibility
    From an external network perspective, test if UDP port 8211 is reachable on the device. Use 'nc -uv <device_ip> 8211' or 'nmap -sU -p 8211 <device_ip>' from an untrusted network segment.
    Affected if UDP port 8211 is exposed and reachable from untrusted networks.
  4. Confirm PAPI service status
    Check if the PAPI (Aruba AP management protocol) service is enabled and listening on the device. Run 'show ip interface' or check the service listening on UDP port 8211.
    Affected if PAPI service is running and listening on UDP port 8211.

The environment is affected if the device is an Aruba SD-WAN or ArubaOS AP running an affected version with UDP port 8211 exposed to untrusted networks.

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-provided patches immediately; if patching is not immediately feasible, restrict network access to UDP port 8211 via firewall or ACLs to prevent unauthenticated attackers from reaching the PAPI service.

Recommended fix High confidence

ArubaOS 8.6.0.20+ / 8.10.0.5+ / 10.3.1.1+; SD-WAN 8.7.0.0-2.3.0.9+

  1. Identify the currently installed ArubaOS or SD-WAN version using 'show version' or the WebUI
  2. For ArubaOS 8.6.x: Upgrade to version 8.6.0.20 or later
  3. For ArubaOS 8.10.x: Upgrade to version 8.10.0.5 or later
  4. For ArubaOS 10.3.x: Upgrade to version 10.3.1.1 or later
  5. For SD-WAN (8.7.0.0-2.3.x): Upgrade to version 8.7.0.0-2.3.0.9 or later
  6. After upgrade, verify the version with 'show version' and confirm the PAPI service is running on UDP port 8211
  7. Review access controls and consider firewall rules to restrict UDP port 8211 to trusted management interfaces only
Caveat Review release notes for your specific model before upgrading; some hardware may have older unsupported versions that require alternative remediation

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 / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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