dbcve.org
ArubaosOperating system · Arubanetworks

CVE-2024-25612

HIGH · 7.2 CVSS v3.1 Published 2024-03-05
Fix available
A fix is available. Upgrade to 8.10.0.10 / 8.11.2.1 or later.
See remediation →
78/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
Authenticated command injection vulnerabilities exist in the ArubaOS command line interface. Successful exploitation of these vulnerabilities result in the ability to execute arbitrary commands as a privileged user 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

Authenticated command injection vulnerabilities in the ArubaOS command line interface allow authenticated users to execute arbitrary commands with elevated privileges on the underlying operating system.

MitigationRestrict CLI access to trusted users only, apply the vendor-provided ArubaOS patch, and audit user accounts for necessity and least-privilege principles.

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
ArubaosOperating system
Affected:>= 8.10.0.0, < 8.10.0.10>= 8.11.0.0, < 8.11.2.1>= 10.4.0.0, < 10.4.1.0>= 10.5.0.0, < 10.5.1.0

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

CVSS:3.1/AV:N/AC:L/PR:H/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 checks

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

  1. Identify the ArubaOS version
    Access the Aruba CLI and run the command 'show version' to display the installed OS version
    Affected if The displayed version falls within these ranges: 8.10.0.0 through 8.10.0.9, 8.11.0.0 through 8.11.2.0, 10.4.0.0 through 10.4.0.9, or 10.5.0.0 through 10.5.0.9
  2. Verify CLI access is enabled
    Confirm that the command-line interface service is accessible on the device; this vulnerability is exploitable through the CLI interface
    Affected if CLI access is available and functional on the device
  3. Confirm authenticated user access
    Review user accounts with CLI access using 'show user-database' or by listing accounts with CLI privileges
    Affected if Any user account exists that can authenticate to the CLI (the vulnerability requires an authenticated session to exploit)
  4. Check for privileged user accounts
    Identify users with elevated or admin-level CLI privileges using 'show privilege' or user role definitions
    Affected if Privileged CLI accounts are present (exploitation allows executing commands with elevated privileges)

You are affected if your ArubaOS version matches any of the listed vulnerable ranges AND CLI access is available to authenticated users on your 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 8.10.0.10 / 8.11.2.1 / 10.4.1.0 or later
Fixed in 8.10.0.108.11.2.110.4.1.0
Interim mitigation

Restrict CLI access to trusted users only, apply the vendor-provided ArubaOS patch, and audit user accounts for necessity and least-privilege principles.

Recommended fix High confidence

ArubaOS 8.10.0.10, 8.11.2.1, 10.4.1.0, or 10.5.1.0 (depending on your version branch)

  1. Identify the current ArubaOS version by running 'show version' in the CLI
  2. Determine which version branch you are currently running (8.10.x, 8.11.x, 10.4.x, or 10.5.x)
  3. Download the appropriate fixed ArubaOS image from the Aruba support portal (www.arubanetworks.com)
  4. Transfer the firmware image to the Aruba device using methods such as SCP, FTP, or USB storage
  5. Verify the integrity of the uploaded image using the 'verify image' command
  6. Schedule a maintenance window as upgrades may cause brief service interruption
  7. Execute the upgrade using the 'upgrade-software' command specifying the image path
  8. After the device reboots, verify the new version with 'show version' and confirm it matches the fixed release
Caveat Standard ArubaOS upgrade considerations apply - review release notes for known issues, ensure controller redundancy if applicable, and backup configuration before upgrading

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

Fix this in Arubaos Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,880
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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