CVE-2022-37894
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 the handling of certain SSID strings by Aruba InstantOS and ArubaOS 10. Successful exploitation of this vulnerability results in the ability to interrupt the normal operation of the affected AP of Aruba InstantOS 6.4.x: 6.4.4.8-4.2.4.20 and below; Aruba InstantOS 6.5.x: 6.5.4.23 and below; Aruba InstantOS 8.6.x: 8.6.0.18 and below; Aruba InstantOS 8.7.x: 8.7.1.9 and below; Aruba InstantOS 8.10.x: 8.10.0.1 and below; ArubaOS 10.3.x: 10.3.1.0 and below; Aruba has released upgrades for Aruba InstantOS that address this security vulnerability.
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 confidenceAn unauthenticated attacker can cause a Denial of Service on affected Aruba InstantOS and ArubaOS 10 access points by sending specially crafted SSID strings that trigger a crash or interruption in normal operation. The vulnerability lies in how the device handles certain SSID names.
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.1>= 6.4.0.0, < 6.4.4.8-4.2.4.21>= 6.5.0.0, < 6.5.4.24>= 8.6.0.0, < 8.6.0.19>= 8.7.0.0, < 8.7.1.10>= 8.10.0.0, < 8.10.0.2all versionsCVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/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 device product and firmware versionLog into the access point CLI or web interface and run 'show version' or check the system information page to identify the exact product name (ArubaOS, Aruba Instant, or Siemens Scalance W1750d) and firmware version.Affected if The device runs ArubaOS 10.3.0.0 through 10.3.1.0, Aruba Instant 6.4.x/6.5.x/8.6.x/8.7.x/8.10.x within the specified version ranges, or any version of Siemens Scalance W1750d.
-
Verify ArubaOS version for CVE-2022-37894For ArubaOS devices, run 'show version' and check if the version falls within >= 10.3.0.0 and < 10.3.1.1. Compare your installed version number against this range.Affected if The installed ArubaOS version is 10.3.0.0 through 10.3.1.0 inclusive.
-
Verify Aruba Instant version for CVE-2022-37894For Aruba Instant APs, run 'show version' or access the Instant UI and check the firmware version. Compare against the affected ranges: 6.4.0.0 to < 6.4.4.8-4.2.4.21, 6.5.0.0 to < 6.5.4.24, 8.6.0.0 to < 8.6.0.19, 8.7.0.0 to < 8.7.1.10, or 8.10.0.0 to < 8.10.0.2.Affected if The installed Aruba Instant version matches any of the listed affected version ranges.
-
Confirm Siemens Scalance W1750d statusIdentify if the device is a Siemens Scalance W1750d by checking the product model number via 'show version' or the physical device label.Affected if The device is a Siemens Scalance W1750d running any firmware version.
-
Check if SSID functionality is enabledRun 'show wlan ssid-profile' or access the wireless configuration section to verify if any SSIDs are configured and enabled on the access point.Affected if The access point has SSID profiles configured and enabled, making it susceptible to specially crafted SSID strings.
The environment is affected if the access point runs ArubaOS 10.3.0.0-10.3.1.0, any Aruba Instant version within the specified 6.4.x/6.5.x/8.6.x/8.7.x/8.10.x ranges, or any Siemens Scalance W1750d firmware, and has SSID functionality enabled.
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 · scoped6.4.4.8-4.2.4.216.5.4.248.6.0.19
Apply the vendor-released upgrades for Aruba InstantOS (6.4.x, 6.5.x, 8.6.x, 8.7.x, 8.10.x) and ArubaOS 10.3.x to address this vulnerability. This is a firmware update to the affected access points.
ArubaOS 10.3.1.1+ | InstantOS 6.4.4.8-4.2.4.21+ | InstantOS 6.5.4.24+ | InstantOS 8.6.0.19+ | InstantOS 8.7.1.10+ | InstantOS 8.10.0.2+ (or latest available)
- Identify the exact Aruba InstantOS or ArubaOS version currently running on the affected access point
- For ArubaOS 10.3.x devices: Upgrade to version 10.3.1.1 or later
- For InstantOS 6.4.x devices: Upgrade to version 6.4.4.8-4.2.4.21 or later (e.g., 6.4.4.8-4.2.4.22 or higher)
- For InstantOS 6.5.x devices: Upgrade to version 6.5.4.24 or later
- For InstantOS 8.6.x devices: Upgrade to version 8.6.0.19 or later
- For InstantOS 8.7.x devices: Upgrade to version 8.7.1.10 or later
- For InstantOS 8.10.x devices: Upgrade to version 8.10.0.2 or later (if available)
- For Scalance W1750d devices: Contact Siemens for firmware updates as all versions are affected
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.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 $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-37894 — 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-2022-37894 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