dbcve.org
Sd WanApplication · Arubanetworks

CVE-2023-22756

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 buffer overflow vulnerabilities in multiple underlying operating system processes that could lead to unauthenticated remote code execution by sending specially crafted packets via the PAPI protocol. 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 · moderate confidence

Multiple buffer overflow vulnerabilities exist in underlying operating system processes that can be exploited via the PAPI protocol through specially crafted packets. These flaws allow unauthenticated attackers to achieve remote code execution with privileged (root/system) user permissions on the affected system.

MitigationApply vendor-provided patches for affected operating systems/processes immediately; if patches are unavailable, disable or restrict access to the PAPI protocol at the network perimeter and implement network segmentation to limit exposure.

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 product and version
    Access the device CLI or management interface and run 'show version' or check the web UI dashboard for the exact firmware version number.
    Affected if The device is Aruba SD-WAN or ArubaOS and the version falls within 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-8.6.0.19, 8.10.0.0-8.10.0.4, or 10.3.0.0-10.3.1.0)
  2. Verify PAPI protocol is enabled
    Check the device configuration for PAPI protocol settings via CLI command 'show papi status' or via the web UI under Protocol settings.
    Affected if PAPI protocol is actively enabled on the device
  3. Confirm PAPI port exposure
    Run 'show ip interface' or check firewall rules to determine if UDP port 8211 (PAPI port) is listening on external or management interfaces.
    Affected if PAPI port 8211 is accessible from untrusted networks or the management interface is exposed externally
  4. Check for recent PAPI-related logs
    Review system logs for PAPI protocol activity using 'show logging' or the log management system, looking for anomalous PAPI packet patterns.
    Affected if There are suspicious PAPI packet logs or connection attempts from untrusted sources

The environment is affected if the device runs an Aruba SD-WAN or ArubaOS version within the listed ranges AND has PAPI protocol enabled and accessible.

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 for affected operating systems/processes immediately; if patches are unavailable, disable or restrict access to the PAPI protocol at the network perimeter and implement network segmentation to limit exposure.

Recommended fix Moderate confidence

Upgrade to ArubaOS 8.6.0.20+ (for 8.6.x), 8.10.0.5+ (for 8.10.x), 10.3.2.0+ (for 10.3.x); SD-WAN 8.7.0.0-2.4.0.0 or later stable release

  1. 1. Identify the exact Aruba device model and current software version using 'show version' or through the WebUI.
  2. 2. For SD-WAN devices running 8.7.0.0-2.3.0.0 through 8.7.0.0-2.3.0.8: upgrade to a version newer than 8.7.0.0-2.3.0.8 (e.g., 8.7.0.0-2.4.0.0 or later stable release).
  3. 3. For ArubaOS devices running 8.6.0.0-8.6.0.19: upgrade to version 8.6.0.20 or later.
  4. 4. For ArubaOS devices running 8.10.0.0-8.10.0.4: upgrade to version 8.10.0.5 or later.
  5. 5. For ArubaOS devices running 10.3.0.0-10.3.1.0: upgrade to version 10.3.2.0 or later.
  6. 6. Download the appropriate firmware from the Aruba support portal (https://asp.arubanetworks.com) using valid support credentials.
  7. 7. Upload the new firmware to the device via WebUI (System > Software > Upload) or CLI ('upgrade-software'),
  8. 8. Reboot the device after upgrade completes and verify the new version is running with 'show version'.
Caveat Review release notes for any compatibility issues or configuration changes between versions before upgrading; test in non-production environment first

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

Fix this in Sd Wan 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-22756 — 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-22756 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