CVE-2025-37177
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 arbitrary file deletion vulnerability has been identified in the command-line interface of mobility conductors running either AOS-10 or AOS-8 operating systems. Successful exploitation of this vulnerability could allow an authenticated remote malicious actor to delete arbitrary files within the affected 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 · moderate confidenceCVE-2025-37177 is an arbitrary file deletion vulnerability in the command-line interface of Aruba Mobility Conductors running AOS-10 or AOS-8. An authenticated remote attacker can exploit this flaw to delete arbitrary files on the affected system, potentially leading to denial of service or data loss.
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>= 6.5.4.0, < 8.10.0.21>= 8.11.0.0, < 8.13.1.1>= 10.3.0.0, < 10.4.1.10>= 10.5.0.0, < 10.7.2.2CVSS 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
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed AOS versionLog into the Aruba Mobility Conductor CLI and run 'show version' or check the controller's web interface under Monitoring > System > Overview to retrieve the AOS firmware version.Affected if The installed version falls within any of these vulnerable ranges: >= 6.5.4.0 and < 8.10.0.21; >= 8.11.0.0 and < 8.13.1.1; >= 10.3.0.0 and < 10.4.1.10; or >= 10.5.0.0 and < 10.7.2.2.
-
Verify CLI access exposureReview the controller's management access settings via 'show mgmt-server' or the web interface under Configuration > Management > Management Interface to determine which IP addresses or networks can reach the CLI.Affected if The CLI is accessible from untrusted or external networks rather than being restricted to a trusted management VLAN or VPN.
-
Check for role-based access control configurationRun 'show role' or inspect the user role definitions under Configuration > Management > Users & Roles in the web interface to see which users have CLI access privileges.Affected if Users with elevated or administrative CLI privileges exist beyond those explicitly required for trusted personnel.
-
Review CLI command logs for file deletion activityExecute 'show logging' or check the system audit logs for commands such as 'delete file', 'rm', or other file removal operations that originate from CLI sessions.Affected if Unrecognized or suspicious file deletion commands appear in the logs, especially from users who should not be performing such operations.
A user is affected if their Aruba Mobility Conductor runs an AOS version within the vulnerable ranges listed and has CLI access exposed to untrusted attackers.
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 · scoped8.10.0.218.13.1.110.4.1.10
Apply available vendor patches for AOS-10 and AOS-8. Restrict CLI access to trusted personnel only via role-based access controls and network segmentation. Monitor for unauthorized CLI access attempts.
Minimum fixed versions: AOS-8: 8.10.0.21 or 8.13.1.1 (depending on branch); AOS-10: 10.4.1.10 or 10.7.2.2 (depending on branch)
- 1. Identify the current ArubaOS version by running 'show version' in the CLI
- 2. Determine which version branch your current installation falls into (AOS-8 or AOS-10)
- 3. For AOS-8 versions: If running >= 6.5.4.0 and < 8.10.0.21, upgrade to 8.10.0.21 or later; If running >= 8.11.0.0 and < 8.13.1.1, upgrade to 8.13.1.1 or later
- 4. For AOS-10 versions: If running >= 10.3.0.0 and < 10.4.1.10, upgrade to 10.4.1.10 or later; If running >= 10.5.0.0 and < 10.7.2.2, upgrade to 10.7.2.2 or later
- 5. Download the appropriate upgrade image from support.hpe.com
- 6. Back up the current configuration using 'write memory' and export configuration via 'show configuration'
- 7. Upload the new firmware to the mobility conductor using 'copy firmware' or via the WebUI
- 8. Initiate the upgrade and verify the new version is running post-reboot
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-37177 — 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-2025-37177 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