CVE-2022-23690
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 in the web-based management interface of AOS-CX could allow a remote unauthenticated attacker to fingerprint the exact version AOS-CX running on the switch. This allows an attacker to retrieve information which could be used to more precisely target the switch for further exploitation in ArubaOS-CX Switches version(s): AOS-CX 10.10.xxxx: 10.10.0002 and below, AOS-CX 10.09.xxxx: 10.09.1020 and below, AOS-CX 10.08.xxxx: 10.08.1060 and below, AOS-CX 10.06.xxxx: 10.06.0200 and below. Aruba has released upgrades for ArubaOS-CX Switch Devices that address this security vulnerability.
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 confidenceThe AOS-CX web-based management interface contains a version information disclosure vulnerability that allows remote unauthenticated attackers to fingerprint the exact software version running on the switch through the management interface. This version disclosure can enable attackers to identify known vulnerabilities in specific AOS-CX versions for targeted exploitation.
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.06.0000, < 10.06.0200>= 10.08.0000, < 10.08.1060>= 10.09.0000, < 10.09.1020>= 10.10.0000, < 10.10.0002CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
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 web-based management interface is exposedCheck if the AOS-CX switch management interface is accessible over HTTP/HTTPS from untrusted networks. Review network firewall rules and access control lists to determine if the web UI (typically ports 80/443) is reachable from outside the trusted management network.Affected if The management interface is accessible from untrusted network segments or the internet.
-
Retrieve AOS-CX software version via CLIConnect to the switch console or management VLAN and execute the command 'show version' to obtain the exact software version number. Note the full version string displayed (e.g., 10.08.1050).Affected if The command executes successfully and returns a version number.
-
Compare version against affected rangesMatch the obtained version number against the vulnerable ranges: 10.06.0000 through 10.06.0199, 10.08.0000 through 10.08.1059, 10.09.0000 through 10.09.1019, or 10.10.0000 through 10.10.0001.Affected if The installed version falls within any of these ranges: >= 10.06.0000 and < 10.06.0200, OR >= 10.08.0000 and < 10.08.1060, OR >= 10.09.0000 and < 10.09.1020, OR >= 10.10.0000 and < 10.10.0002.
-
Verify version disclosure via web interface probeSend an HTTP GET request to the management interface endpoint (such as the login page or a version info endpoint) and inspect the response headers or body for version information. Tools like curl or a browser's developer console can be used to capture and examine these responses.Affected if The web interface response contains or leaks the exact AOS-CX software version number.
You are affected if the AOS-CX web management interface is exposed to untrusted networks and the switch runs a version matching any of the four vulnerable ranges listed in the CVE.
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.06.020010.08.106010.09.1020
Upgrade AOS-CX switches to patched versions: 10.10.0003 or higher, 10.09.1021 or higher, 10.08.1061 or higher, or 10.06.0201 or higher as specified in the Aruba security advisory.
AOS-CX 10.06.0200 or later; 10.08.1060 or later; 10.09.1020 or later; 10.10.0002 or later (depending on your version branch)
- Identify the currently running AOS-CX version on the switch using 'show version' command
- Determine which version branch your switch is running (10.06.x, 10.08.x, 10.09.x, or 10.10.x)
- Download the appropriate fixed firmware version from Aruba's support portal: 10.06.0200 or later for 10.06 branch, 10.08.1060 or later for 10.08 branch, 10.09.1020 or later for 10.09 branch, or 10.10.0002 or later for 10.10 branch
- Upload the new firmware to the switch using 'copy tftp://<server>/<file> system:?' or via WebUI/Aruba CX Mobility Console
- Verify the firmware image is stored properly using 'show flash'
- Schedule a maintenance window as firmware upgrade will cause brief network disruption
- Execute the upgrade using 'boot system <image>' command or via WebUI
- After reboot, verify the new version is installed using 'show version' and confirm the version is at or above the fixed release for your branch
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-23690 — 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-23690 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