CVE-2025-37169
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 · uneditedA stack overflow vulnerability exists in the AOS-10 web-based management interface of a Mobility Gateway. Successful exploitation could allow an authenticated malicious actor to execute arbitrary code 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 · moderate confidenceA stack overflow vulnerability in the AOS-10 web-based management interface of a Mobility Gateway allows an authenticated attacker to execute arbitrary code with elevated privileges. The vulnerability stems from improper bounds checking on user input processed by the web interface, enabling buffer overflow on the stack.
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>= 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.
-
Confirm device is an Aruba Mobility Gateway running ArubaOSAccess the device CLI and run 'show version' or 'show system', or check the web management interface for product identificationAffected if Device is not an Aruba Mobility Gateway or does not run ArubaOS - this CVE does not apply
-
Check the installed ArubaOS versionRun 'show version' in the device CLI or look for the firmware version displayed in the web interface footer or system info pageAffected if Version is 10.3.0.0 through 10.4.1.9, OR 10.5.0.0 through 10.7.2.1 (within the affected ranges)
-
Verify the web-based management interface is enabledRun 'show web-server' or 'show running-config | include web' in the CLI to check if the HTTP/HTTPS management service is activeAffected if Web management interface is enabled - this is required for the vulnerable code path to be reachable
-
Confirm management interface accessibilityReview interface bindings and access lists via 'show ip interface' or 'show access-list' to determine if the web interface is exposed beyond trusted networksAffected if The web management interface is reachable from untrusted or external networks (not restricted to trusted IPs)
-
Review authentication configuration for management interfaceCheck user accounts and authentication settings via 'show user-table' or 'show aaa authentication-server' to understand who can access the management interfaceAffected if Multiple accounts exist or weak credentials are configured, allowing potential authenticated attacker access
You are affected if you have an Aruba Mobility Gateway on ArubaOS versions 10.3.0.0-10.4.1.9 or 10.5.0.0-10.7.2.1 with the web-based management interface enabled and accessible to an authenticated user.
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 · scoped10.4.1.1010.7.2.2
Apply vendor-provided patches for AOS-10 when available. Until then, restrict access to the management interface to trusted IP addresses and use strong authentication credentials to reduce the attack surface.
ArubaOS 10.4.1.10 or later (for 10.3.x branch); ArubaOS 10.7.2.2 or later (for 10.5.x-10.7.x branches)
- Identify the current ArubaOS version by checking the web-based management interface or using 'show version' command
- Determine which upgrade path applies based on current version: if running 10.3.x, upgrade to 10.4.1.10 or later; if running 10.5.x through 10.7.1.x, upgrade to 10.7.2.2 or later
- Download the appropriate fixed ArubaOS version from support.hpe.com
- Review the upgrade guide for proper upgrade procedure, including any required pre-upgrade checks
- Perform the upgrade during a planned maintenance window
- After upgrade, verify the new version is installed and the web-based management interface is functional
- Confirm the vulnerability is remediated
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-37169 — 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-37169 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