CVE-2023-45621
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 · uneditedUnauthenticated Denial-of-Service (DoS) vulnerabilities exist in the CLI service accessed via the PAPI protocol. Successful exploitation of these vulnerabilities result 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 confidenceThis is an unauthenticated Denial-of-Service vulnerability affecting the CLI service exposed via the PAPI (Protocol API) protocol on network access points. An attacker can send specially crafted packets to the PAPI service to crash or hang the CLI service, causing the access point to become unresponsive or require a reboot.
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.4.0.3= 10.5.0.0>= 6.4.0.0, < 8.6.0.23>= 8.10.0.0, < 8.10.0.9>= 8.11.0.0, < 8.11.2.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
- 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 firmware versionExecute 'show version' on the CLI or check the WebUI dashboard for the ArubaOS or InstantOS version numberAffected if The version falls within >= 10.3.0.0, < 10.4.0.3; = 10.5.0.0 for ArubaOS or >= 6.4.0.0, < 8.6.0.23; >= 8.10.0.0, < 8.10.0.9; >= 8.11.0.0, < 8.11.2.0 for InstantOS
-
Verify PAPI service statusRun 'show papi status' or check the CLI configuration for PAPI (Protocol API) service settings. The service typically listens on UDP port 8211Affected if PAPI/CLI service is enabled and running on the device
-
Check network exposure of UDP port 8211Review firewall rules, ACLs, or VLAN configuration to determine if UDP port 8211 (PAPI) is reachable from untrusted or external networks. Use 'show ip interface' and review any access-list configurations applied to the management or data interfacesAffected if UDP port 8211 is accessible from untrusted network segments or the internet
You are affected if your device runs a vulnerable ArubaOS or InstantOS version, the PAPI service is enabled, and UDP port 8211 is reachable from an attacker-controlled network segment.
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.
dbcve · scoped8.6.0.238.10.0.98.11.2.0
Restrict network access to the PAPI/CLI service using firewalls or ACLs, and apply vendor firmware updates when available. If PAPI is not required, disable the service.
ArubaOS: 10.4.0.3+ or 10.5.0.1+; InstantOS: 8.6.0.23+, 8.10.0.9+, or 8.11.2.0+
- Identify the currently installed ArubaOS or InstantOS version using 'show version' command
- For ArubaOS 10.3.x.x - 10.4.x: Upgrade to version 10.4.0.3 or later
- For ArubaOS 10.5.0.0: Upgrade to version 10.5.0.1 or later (the next available patch)
- For InstantOS 6.4.x.x - 8.6.x: Upgrade to version 8.6.0.23 or later
- For InstantOS 8.10.x.x: Upgrade to version 8.10.0.9 or later
- For InstantOS 8.11.x.x: Upgrade to version 8.11.2.0 or later
- Upgrade via Aruba's management interface or CLI using 'upgrade-software' command
- After upgrade, verify the new version is installed with 'show version'
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-45621 — 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-45621 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