CVE-2022-37893
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 authenticated command injection vulnerability exists in the Aruba InstantOS and ArubaOS 10 command line interface. Successful exploitation of this vulnerability results in the ability to execute arbitrary commands as a privileged user on the underlying operating system 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 confidenceAuthenticated command injection vulnerability in Aruba InstantOS and ArubaOS command line interface allows an authenticated attacker to execute arbitrary commands as a privileged (root) user on the underlying operating system due to insufficient input validation in CLI commands.
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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device product and modelAccess the device CLI or web interface and run 'show version' or check the system information page to identify if the device is Aruba Instant, ArubaOS, or Siemens Scalance W1750dAffected if The device is Aruba Instant, ArubaOS, or Siemens Scalance W1750d
-
Check ArubaOS versionRun 'show version' in the ArubaOS CLI and note the software version numberAffected if The installed ArubaOS version is 10.3.0.0 through 10.3.1.0 (anything >= 10.3.0.0 but < 10.3.1.1)
-
Check Aruba Instant versionRun 'show version' in the Aruba Instant CLI and note the software version numberAffected if The installed Aruba Instant version falls within any of these ranges: >= 6.4.0.0 but < 6.4.4.8-4.2.4.21, >= 6.5.0.0 but < 6.5.4.24, >= 8.6.0.0 but < 8.6.0.19, >= 8.7.0.0 but < 8.7.1.10, or >= 8.10.0.0 but < 8.10.0.2
-
Check Siemens Scalance W1750d firmware versionAccess the Scalance W1750d web interface or CLI and identify the firmware versionAffected if Any firmware version is installed (all versions of this device are affected)
-
Verify CLI access is availableConfirm the device CLI is accessible via console, SSH, or telnet (the vulnerability requires an authenticated CLI session to exploit)Affected if CLI access exists and the device version matches the affected ranges above
The device is affected if it is running ArubaOS < 10.3.1.1, Aruba Instant in any of the listed affected version ranges, or any version of Siemens Scalance W1750d firmware, and the CLI interface is accessible for authenticated exploitation.
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
Upgrade to patched versions of Aruba InstantOS (6.4.4.8-4.2.4.21+, 6.5.4.24+, 8.6.0.19+, 8.7.1.10+, 8.10.0.2+) and ArubaOS 10.3.1.1+ as specified in the Aruba security advisory.
ArubaOS 10.3.1.1+; Aruba InstantOS 6.4.4.8-4.2.4.21+; 6.5.4.24+; 8.6.0.19+; 8.7.1.10+; contact Siemens for Scalance W1750d
- 1. Identify the exact Aruba product line and current firmware version using 'show version' or 'get version' CLI command
- 2. For ArubaOS 10.3.x: Upgrade to version 10.3.1.1 or later
- 3. For Aruba InstantOS 6.4.x: Upgrade to version 6.4.4.8-4.2.4.21 or later
- 4. For Aruba InstantOS 6.5.x: Upgrade to version 6.5.4.24 or later
- 5. For Aruba InstantOS 8.6.x: Upgrade to version 8.6.0.19 or later
- 6. For Aruba InstantOS 8.7.x: Upgrade to version 8.7.1.10 or later
- 7. For Scalance W1750d: Contact Siemens for available firmware updates; no fix currently documented
- 8. After upgrade, verify the fix by checking 'show version' confirms the patched version is installed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-37893 — 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-37893 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