CVE-2023-22754
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 · uneditedThere 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 confidenceMultiple buffer overflow vulnerabilities exist in underlying OS processes that can be exploited via the PAPI protocol. Unauthenticated attackers can send specially crafted packets to achieve remote code execution as a privileged user.
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>= 8.7.0.0-2.3.0.0, <= 8.7.0.0-2.3.0.8>= 8.6.0.0, <= 8.6.0.19>= 8.10.0.0, <= 8.10.0.4>= 10.3.0.0, <= 10.3.1.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Aruba product typeDetermine if the system is running Aruba SD-WAN or ArubaOS by checking the system hostname, model, or running 'show version' commandAffected if The product is Aruba SD-WAN or ArubaOS
-
Check the installed ArubaOS versionRun 'show version' or 'show system information' to retrieve the OS version numberAffected if Version is 8.6.0.0 through 8.6.0.19, 8.10.0.0 through 8.10.0.4, 10.3.0.0 through 10.3.1.0, or SD-WAN version 8.7.0.0-2.3.0.0 through 8.7.0.0-2.3.0.8
-
Verify PAPI protocol statusCheck if the PAPI protocol interface is enabled or exposed. On Aruba devices, this is typically UDP port 8211. Use 'show papi status' or check firewall rules for inbound access to UDP 8211 from untrusted networksAffected if PAPI protocol (UDP port 8211) is accessible from untrusted network segments or the internet
-
Check network exposure of PAPI serviceReview network firewall or ACL configurations to determine if UDP port 8211 (PAPI) is open to external or untrusted IP addressesAffected if PAPI port 8211 accepts traffic from outside the trusted management network
You are affected if you run Aruba SD-WAN (8.7.0.0-2.3.0.0 to 8.7.0.0-2.3.0.8) or 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) AND the PAPI protocol interface is network-accessible to untrusted hosts.
Generated from the published advisory. Verify against your own configuration.
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 dataApply available patches or updates from the affected product vendor; if no patch exists, implement network segmentation to restrict access to PAPI protocol interfaces.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-22754 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-22754 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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