CVE-2025-37175
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 upload vulnerability exists in the web-based management interface of mobility conductors running either AOS-10 or AOS-8 operating systems. Successful exploitation could allow an authenticated malicious actor to upload arbitrary files as a privilege user and execute arbitrary commands 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 confidenceArbitrary file upload vulnerability in the web-based management interface of mobility conductors running AOS-10 or AOS-8. An authenticated attacker with management access can upload arbitrary files as a privileged user and execute commands on the underlying operating system, achieving remote code execution with elevated privileges.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed AOS versionAccess the mobility conductor CLI and run 'show version' or check the web management interface dashboard for the AOS version numberAffected if The version falls within any of these 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; >= 10.5.0.0 and < 10.7.2.2
-
Confirm web-based management interface is enabledCheck the device configuration for 'web-server' or 'https-server' settings via 'show running-config | include web' or inspect the management interface access listAffected if The web-based management interface (HTTP/HTTPS) is accessible and enabled on the device
-
Verify management user accessReview the list of configured management users with administrative privileges using 'show user-database' or through the web interface user management sectionAffected if Multiple management accounts exist or accounts with elevated privileges are present, increasing the attack surface
-
Review web server logs for suspicious upload activityInspect web management logs or system logs for unusual file upload requests, atypical file types, or unexpected POST requests to upload endpoints
You are affected if your Aruba mobility conductor runs an AOS version within the affected ranges AND has the web-based management interface enabled with management user accounts accessible to 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 the vendor-supplied patch or upgrade to a fixed AOS-10 or AOS-8 version. Restrict web management interface access to trusted administrators only and monitor for suspicious file upload activity.
Upgrade to ArubaOS 8.10.0.21+/8.13.1.1+ (AOS-8) or 10.4.1.10+/10.7.2.2+ (AOS-10) based on your current branch
- 1. Identify the currently installed ArubaOS version by navigating to the web-based management interface or using 'show version' command
- 2. Determine which version branch your current installation falls into (AOS-8 or AOS-10)
- 3. Access the HPE Aruba support portal at support.hpe.com and download the appropriate fixed version for your branch
- 4. For AOS-8: upgrade to version 8.10.0.21 or higher, or 8.13.1.1 or higher depending on your branch
- 5. For AOS-10: upgrade to version 10.4.1.10 or higher, or 10.7.2.2 or higher depending on your branch
- 6. Back up the current configuration using 'backup flash' or via the web interface
- 7. Upload the new firmware image through the web-based management interface or via the CLI
- 8. Reload the system to apply the new firmware
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-37175 — 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-37175 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