CVE-2025-37168
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 · uneditedArbitrary file deletion vulnerability have been identified in a system function of mobility conductors running AOS-8 operating system. Successful exploitation of this vulnerability could allow an unauthenticated remote malicious actor to delete arbitrary files within the affected system and potentially result in denial-of-service conditions on affected devices.
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 confidenceArbitrary file deletion vulnerability in Aruba mobility conductors running AOS-8 allows unauthenticated remote attackers to delete any files on the affected system, potentially causing denial-of-service conditions.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify device as Aruba mobility conductor running AOS-8Access the device CLI and run 'show version' or 'show system info' to confirm the device is an Aruba mobility conductor and note the operating system nameAffected if The device is not an Aruba mobility conductor running AOS-8 (the vulnerability only affects this specific product)
-
Determine installed AOS-8 versionFrom the 'show version' output, locate the firmware/software version string (typically labeled as 'Version' or 'AOS-W')Affected if Unable to retrieve the AOS-8 version number from the device
-
Compare version against affected rangesCompare your installed AOS-8 version to these vulnerable ranges: 6.5.4.0 through 8.10.0.20, 8.11.0.0 through 8.13.1.0, 10.3.0.0 through 10.4.1.9, and 10.5.0.0 through 10.7.2.1Affected if The installed version falls within any of these ranges (>=6.5.4.0 and <8.10.0.21, OR >=8.11.0.0 and <8.13.1.1, OR >=10.3.0.0 and <10.4.1.10, OR >=10.5.0.0 and <10.7.2.2)
-
Verify management interface accessibilityCheck if the Aruba web management interface (HTTPS port 4343) or API endpoint is reachable from untrusted networks by reviewing firewall rules or performing a port scan of the management interfaceAffected if The management interface is exposed to untrusted networks without network access controls (the vulnerability is exploitable by unauthenticated remote attackers)
The environment is affected if it is an Aruba mobility conductor running a version of AOS-8 that falls within the affected version ranges AND the management interface is accessible to potential 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 vendor-provided ArubaOS-8 security patches immediately; restrict management interface exposure to untrusted networks until patches are deployed.
Upgrade to the minimum fixed version for your branch: 8.10.0.21 (8.10.x), 8.13.1.1 (8.11-8.13.x), 10.4.1.10 (10.3-10.4.x), or 10.7.2.2 (10.5-10.7.x)
- 1. Identify the currently running ArubaOS version on the mobility conductor by navigating to Maintenance > Files > Software, or using 'show version' command
- 2. Determine which version branch the current installation falls into: 8.10.x, 8.11.x-8.13.x, 10.3.x-10.4.x, or 10.5.x-10.7.x
- 3. For 8.10.x branch: upgrade to version 8.10.0.21 or later in the 8.10.x line
- 4. For 8.11.x-8.13.x branch: upgrade to version 8.13.1.1 or later in the 8.13.x line
- 5. For 10.3.x-10.4.x branch: upgrade to version 10.4.1.10 or later in the 10.4.x line
- 6. For 10.5.x-10.7.x branch: upgrade to version 10.7.2.2 or later in the 10.7.x line
- 7. Download the appropriate upgrade image from support.hpe.com and upload to the mobility conductor
- 8. Before upgrading, backup configuration using 'backup flash' or via WebUI
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-37168 — 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-37168 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