dbcve.org
ArubaosOperating system · Arubanetworks

CVE-2024-25614

CRITICAL · 9.1 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 →
100/100
Remediation priority · Urgent
Remotely reachable 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
There is an arbitrary file deletion vulnerability in the CLI used by ArubaOS. Successful exploitation of this vulnerability results in the ability to delete arbitrary files on the underlying operating system, which could lead to denial-of-service conditions and impact the integrity of the controller.

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

An arbitrary file deletion vulnerability exists in the ArubaOS CLI that allows authenticated attackers to delete arbitrary files on the underlying operating system. By exploiting insufficient path validation in CLI commands, an attacker can remove critical system files, causing denial of service and compromising the integrity of the wireless controller.

MitigationApply the Aruba Networks firmware update addressing CVE-2024-25614 immediately. Restrict CLI access to authenticated, trusted administrators only and monitor for unauthorized file deletion attempts.

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Check the installed ArubaOS version
    Access the Aruba controller CLI and run: show version | include Version or show controller-info | include version
    Affected if The displayed version falls within these ranges: 8.10.0.0 to 8.10.0.9, 8.11.0.0 to 8.11.2.0, 10.4.0.0 to 10.4.0.9, or 10.5.0.0 to 10.5.1.0
  2. Confirm CLI access is available
    Verify you can access the ArubaOS command-line interface via console, SSH, or Telnet
    Affected if CLI access is enabled and reachable on the controller
  3. Review system audit logs for file deletion commands
    Run: show audit-log or show logging | include delete to examine recent CLI commands that deleted files
    Affected if Log entries show unexpected or unauthorized file deletion commands targeting system files outside normal operations
  4. Check for modified or missing critical system files
    Compare outputs of show flash or dir /flash against known-good baselines; look for missing configuration or system files
    Affected if Critical system files are missing or modified without documented cause

The environment is affected if the ArubaOS version falls within the four vulnerable ranges and the CLI interface is accessible, regardless of whether exploitation has occurred.

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

Apply the Aruba Networks firmware update addressing CVE-2024-25614 immediately. Restrict CLI access to authenticated, trusted administrators only and monitor for unauthorized file deletion attempts.

Recommended fix High confidence

Upgrade to 8.10.0.10 (for 8.10.x branch), 8.11.2.1 (for 8.11.x branch), 10.4.1.0 (for 10.4.x branch), or 10.5.1.0 (for 10.5.x branch) depending on your current branch

  1. 1. Identify the currently running ArubaOS version using 'show version' command in the CLI
  2. 2. Determine which version branch you are on (8.10.x, 8.11.x, 10.4.x, or 10.5.x)
  3. 3. Download the appropriate fixed version from Aruba Networks support portal: for 8.10.x branch use 8.10.0.10, for 8.11.x use 8.11.2.1, for 10.4.x use 10.4.1.0, for 10.5.x use 10.5.1.0
  4. 4. Upload the ArubaOS firmware file to the controller via SCP, FTP, or the WebUI
  5. 5. Verify the MD5/SHA256 checksum of the uploaded file matches the published checksum
  6. 6. Execute 'upgrade-software <filename>' command in CLI to initiate the upgrade
  7. 7. After upgrade completes, verify the new version using 'show version' and confirm the fix is applied
  8. 8. Test that the arbitrary file deletion vulnerability is no longer exploitable
Caveat Review ArubaOS release notes for any configuration or feature changes between your current version and the target fixed version before upgrading

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

Fix this in Arubaos Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
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,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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