dbcve.org
Sd WanApplication · Arubanetworks

CVE-2022-37909

MEDIUM · 5.3 CVSS v3.1 Published 2022-12-12
Fix available
A fix is available. Upgrade to 6.5.4.22 / 8.6.0.17 or later.
See remediation →
58/100
Remediation priority · Elevated
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
Aruba has identified certain configurations of ArubaOS that can lead to sensitive information disclosure from the configured ESSIDs. The scenarios in which disclosure of potentially sensitive information can occur are complex, and depend on factors beyond the control of attackers.

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

ArubaOS contains a configuration-dependent information disclosure vulnerability where sensitive information from configured ESSIDs (Extended Service Set Identifiers) can be exposed. The complexity of the disclosure scenarios depends on factors beyond attacker control, suggesting this may involve specific wireless configurations or network topologies.

MitigationReview ArubaOS configuration settings related to ESSID broadcasting and management interfaces, and apply any available vendor patches for this vulnerability.

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.6
ArubaosOperating system
Affected:>= 6.5.4.0, < 6.5.4.22>= 8.4.0.0, < 8.6.0.17>= 8.7.0.0, < 8.7.1.9>= 8.8.0.0, < 10.3.0.1

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
Adjacent
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

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 installed ArubaOS version
    Access the Aruba device CLI and run 'show version' or 'show controller, or access the web UI and check the Dashboard or About page for the firmware version
    Affected if The version falls within: 6.5.4.0 to 6.5.4.21, 8.4.0.0 to 8.6.0.16, 8.7.0.0 to 8.7.1.8, 8.8.0.0 to 10.3.0.0, or for SD-WAN: 8.7.0.0-2.3.0.0 to 8.7.0.0-2.3.0.5
  2. Verify wireless functionality is configured
    In the CLI run 'show wlan ssid-profile' or 'show wlan virtual-ap' to list configured wireless networks. In the web UI, navigate to Configuration > Wireless > SSID Profiles
    Affected if Wireless SSID profiles are defined on the device, making ESSID information potentially accessible
  3. Check for sensitive ESSID configurations
    Review the output from 'show wlan ssid-profile' and look for ESSIDs that may contain sensitive information such as pre-shared keys embedded in names, corporate identifiers, or internal network references
    Affected if Configured ESSIDs contain sensitive information in their names or associated configurations that could be exposed
  4. Verify management interface exposure
    Check 'show ip interface' and 'show running-config' to determine if management interfaces are accessible from untrusted networks, which could enable an attacker to trigger the information disclosure
    Affected if Management interfaces are exposed to untrusted networks, increasing the likelihood of exploitation

You are affected if your ArubaOS version matches the affected ranges AND wireless ESSID profiles are configured on the device.

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 6.5.4.22 / 8.6.0.17 / 8.7.0.0-2.3.0.6 or later
Fixed in 6.5.4.228.6.0.178.7.0.0-2.3.0.6
Interim mitigation

Review ArubaOS configuration settings related to ESSID broadcasting and management interfaces, and apply any available vendor patches for this vulnerability.

Recommended fix High confidence

ArubaOS: 6.5.4.22+, 8.6.0.17+, 8.7.1.9+, 10.3.0.1+ | SD-WAN: 8.7.0.0-2.3.0.6+

  1. 1. Identify the exact ArubaOS or SD-WAN version currently running on the affected device
  2. 2. Determine which branch (SD-WAN or specific ArubaOS version) the device is running
  3. 3. For SD-WAN devices: Plan upgrade to version 8.7.0.0-2.3.0.6 or later
  4. 4. For ArubaOS 6.5.x devices: Plan upgrade to version 6.5.4.22 or later
  5. 5. For ArubaOS 8.4.x to 8.5.x devices: Plan upgrade to version 8.6.0.17 or later
  6. 6. For ArubaOS 8.7.x devices: Plan upgrade to version 8.7.1.9 or later
  7. 7. For ArubaOS 8.8.x to 9.x devices: Plan upgrade to version 10.3.0.1 or later
  8. 8. Review upgrade procedure in Aruba product documentation

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

Fix this in Sd Wan Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $2,000
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-37909 — 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-2022-37909 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