dbcve.org
Sd WanApplication · Arubanetworks

CVE-2022-37906

HIGH · 8.1 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 →
87/100
Remediation priority · High
Remotely reachable 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
An authenticated path traversal vulnerability exists in the ArubaOS command line interface. Successful exploitation of the vulnerability results in the ability to delete arbitrary files 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 · high confidence

CVE-2022-37906 is an authenticated path traversal vulnerability in the ArubaOS command line interface that allows authenticated attackers to delete arbitrary files on the underlying operating system by manipulating file paths in CLI commands.

MitigationApply the relevant Aruba security patch for CVE-2022-37906; ensure CLI access is restricted to authorized administrators and monitor for suspicious file deletion commands in audit logs.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify product and version
    Access the device CLI or web interface and run 'show version' or check the web UI dashboard to determine if the device runs ArubaOS or Aruba SD-WAN and note the exact firmware version number
    Affected if The product is ArubaOS or Aruba SD-WAN and the version falls within one of the affected ranges: ArubaOS 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 Aruba SD-WAN 8.7.0.0-2.3.0.0 to 8.7.0.0-2.3.0.5
  2. Verify CLI access is enabled
    Check the device configuration for CLI access methods: review 'show ip ssh' or 'show telnet' in privileged mode, and check the web UI under Configuration > Management > CLI Settings to confirm CLI access is enabled
    Affected if CLI access (SSH, Telnet, or Web CLI) is enabled, as the vulnerability requires authenticated CLI access to exploit the path traversal
  3. Review user accounts with CLI privileges
    Execute 'show users' or 'show aaa authentication local-user' in the CLI to list accounts with CLI access, and cross-reference with your authorized administrator list to identify any unexpected accounts
    Affected if There are unauthorized or unexpected user accounts with CLI access, which could indicate compromise or misuse of the vulnerability
  4. Inspect audit logs for file deletion commands
    Run 'show audit-log' or access the device logs via the web UI under Monitoring > Logs and search for commands containing patterns like 'delete', 'rm', 'rmdir', or path traversal indicators such as '../' targeting sensitive directories
    Affected if Audit logs show file deletion CLI commands that target paths outside normal operational directories, especially from accounts that should not be performing such operations

A device is affected if it runs a vulnerable ArubaOS or Aruba SD-WAN version AND has CLI access enabled, allowing an authenticated attacker to manipulate file paths and delete arbitrary files.

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

Apply the relevant Aruba security patch for CVE-2022-37906; ensure CLI access is restricted to authorized administrators and monitor for suspicious file deletion commands in audit logs.

Recommended fix High confidence

ArubaOS: 6.5.4.22, 8.6.0.17, 8.7.1.9, or 10.3.0.1 (depending on current branch); SD-WAN: 8.7.0.0-2.3.0.6

  1. 1. Identify the currently installed ArubaOS version by running 'show version' in the CLI
  2. 2. Based on the current version, determine the appropriate fixed release: For Sd Wan 8.7.0.0-2.3.x upgrade to 8.7.0.0-2.3.0.6; For ArubaOS 6.5.4.x upgrade to 6.5.4.22; For ArubaOS 8.4.x-8.6.x upgrade to 8.6.0.17; For ArubaOS 8.7.x upgrade to 8.7.1.9; For ArubaOS 8.8.x-10.2.x upgrade to 10.3.0.1
  3. 3. Download the appropriate firmware upgrade file from the Aruba support portal at www.arubanetworks.com
  4. 4. Back up the current configuration using 'backup flash' or 'write mem' commands
  5. 5. Upload the firmware to the controller using 'copy tftp://<server>/<file> flash:' or via the WebUI
  6. 6. Reboot the device into the new firmware using 'reload' command
  7. 7. Verify the upgrade was successful and the vulnerability is patched by confirming the new version is installed
Caveat Major version upgrades (e.g., 8.x to 10.x) may require configuration changes or have feature differences; always review release notes before upgrading

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

Fix this in Sd Wan Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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 locally
dbcve dependency scanner

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