CVE-2023-22787
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 · uneditedAn unauthenticated Denial of Service (DoS) vulnerability exists in a service accessed via the PAPI protocol provided by Aruba InstantOS and ArubaOS 10. Successful exploitation of this vulnerability results in the ability to interrupt the normal operation of the affected access point.
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 confidenceAn unauthenticated attacker can exploit a vulnerability in the PAPI (Provisioning Access Protocol) service on Aruba InstantOS and ArubaOS 10 to cause a Denial of Service on affected access points. The vulnerability requires no authentication, allowing remote attackers to disrupt normal AP operations.
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>= 10.3.0.0, <= 10.3.1.0>= 6.4.0.0, <= 6.4.4.8-4.2.4.20>= 6.5.0.0, <= 6.5.4.23>= 8.4.0.0, < 8.6.0.0>= 8.6.0.0, <= 8.6.0.19>= 8.7.0.0, <= 8.9.0.0>= 8.10.0.0, <= 8.10.0.4CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 installed ArubaOS or InstantOS versionRun 'show version' or 'get version' on the access point or controller CLI to retrieve the firmware versionAffected if The version falls within any of these ranges: ArubaOS 10.3.0.0-10.3.1.0; InstantOS 6.4.0.0-6.4.4.8-4.2.4.20; InstantOS 6.5.0.0-6.5.4.23; InstantOS 8.4.0.0-8.5.9.9; InstantOS 8.6.0.0-8.6.0.19; InstantOS 8.7.0.0-8.9.0.0; InstantOS 8.10.0.0-8.10.0.4
-
Confirm the PAPI service is enabledRun 'show papi status' or check the PAPI configuration via 'show running-config | include papi' on the CLIAffected if The PAPI (Provisioning Access Protocol) service is listed as enabled or running on the device
-
Verify PAPI service is listening on the networkCheck for open ports associated with PAPI (typically UDP port 8211) using 'show ip interface' or port scanning from an adjacent hostAffected if The PAPI port is open and reachable on the network interface, indicating the service is exposed to potential remote attackers
The environment is affected if the device runs a version within the specified ranges AND the PAPI service is enabled and network-accessible, allowing unauthenticated remote attackers to trigger denial of service.
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 data8.6.0.0
Apply the vendor-provided security update for Aruba InstantOS and ArubaOS 10. If no patch is immediately available, consider network segmentation to limit PAPI protocol exposure and monitor for indicators of compromise.
- Consultation4.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,872.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-22787 — 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-22787 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