CVE-2022-37903
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 vulnerability exists that allows an authenticated attacker to overwrite an arbitrary file with attacker-controlled content via the web interface. Successful exploitation of this vulnerability could lead to full compromise the underlying host 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 confidenceThis is an authenticated arbitrary file write vulnerability in a web interface that allows an attacker with valid credentials to overwrite any file on the system with content they control. This can be exploited to modify configuration files, deploy malicious scripts, or overwrite system files to achieve full operating system compromise.
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>= 8.7.0.0-2.3.0.0, < 8.7.0.0-2.3.0.7>= 6.5.4.0, < 6.5.4.23>= 8.4.0.0, < 8.6.0.18>= 8.7.0.0, < 8.7.1.10>= 8.8.0.0, <= 8.9.0.3= 10.3.0.0CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 product type and versionAccess the web interface or CLI and retrieve the system version information. For SD-WAN, look in the main dashboard or system settings. For ArubaOS, use 'show version' command in CLI or check the web UI footer/About page.Affected if The installed version falls within any of these ranges: SD-WAN >= 8.7.0.0-2.3.0.0 and < 8.7.0.0-2.3.0.7; ArubaOS 6.5.4.0 to < 6.5.4.23; 8.4.0.0 to < 8.6.0.18; 8.7.0.0 to < 8.7.1.10; 8.8.0.0 to <= 8.9.0.3; or exactly 10.3.0.0
-
Confirm web interface is enabledCheck if the web-based management interface (GUI) is accessible and enabled on the device. In ArubaOS, use 'show web-server' or check the HTTP/HTTPS service status. In SD-WAN, check the web portal configuration.Affected if The web interface is accessible from the network and accepts authentication requests. The vulnerability requires the web interface to be enabled.
-
Verify authentication is configuredConfirm that valid user accounts exist and can authenticate to the web interface. Check user accounts via CLI command 'show user-database' or through the web interface user management page.Affected if User accounts are created and authentication to the web interface is possible. This is an authenticated vulnerability, so valid credentials are required for exploitation.
-
Check file upload/write functionalityIf you have access, examine the web interface for file upload, configuration import, or backup/restore features that handle file writes. These are the potential attack vectors for this vulnerability.Affected if The web interface exposes any feature that accepts file content and writes it to the filesystem, particularly configuration import, backup restore, or certificate upload features.
You are affected if you run ArubaOS or SD-WAN within the version ranges listed AND the web interface is enabled and accessible with valid user accounts.
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 · scoped6.5.4.238.6.0.188.7.0.0-2.3.0.7
Implement strict input validation and sanitization on all file write operations, enforce proper path traversal checks, and restrict file write capabilities to authorized directories only. Consider implementing allowlist-based file access controls.
ArubaOS: 6.5.4.23+, 8.6.0.18+, 8.7.1.10+, or 8.9.0.4+ (depending on current branch); SD-WAN: 8.7.0.0-2.3.0.7+
- Identify the exact ArubaOS or SD-WAN version currently running on the affected device
- For ArubaOS devices: Upgrade to version 6.5.4.23 or later for the 6.5.4.x branch
- For ArubaOS devices: Upgrade to version 8.6.0.18 or later for the 8.4.x-8.6.x branch
- For ArubaOS devices: Upgrade to version 8.7.1.10 or later for the 8.7.x branch
- For ArubaOS devices: Upgrade to version 8.9.0.4 or later for the 8.8.x-8.9.x branch
- For SD-WAN devices: Upgrade to version 8.7.0.0-2.3.0.7 or later
- Verify the upgrade was successful and the vulnerability is remediated
- Ensure strong authentication is in place even after patching as this vulnerability requires authenticated access
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-37903 — 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-2022-37903 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