dbcve.org
ExosOperating system · Extremenetworks

CVE-2023-43118

HIGH · 8.8 CVSS v3.1 Published 2023-10-16
Fix available
A fix is available. Upgrade to 31.7.2 / 32.5.1.5 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
Cross Site Request Forgery (CSRF) vulnerability in Chalet application in Extreme Networks Switch Engine (EXOS) before 32.5.1.5, fixed in 31.7.2 and 32.5.1.5 allows attackers to run arbitrary code and cause other unspecified impacts via /jsonrpc API.

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 confidence

CSRF vulnerability in the Chalet web application's /jsonrpc API in Extreme Networks EXOS switches allows attackers to craft malicious requests that authenticated users unknowingly execute, potentially leading to arbitrary code execution.

MitigationUpgrade EXOS to version 31.7.2 or 32.5.1.5 or later; implement anti-CSRF tokens for API endpoints.

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
ExosOperating system
Affected:>= 31.7.0, < 31.7.2>= 32.0, < 32.5.1.5

CVSS 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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the EXOS version running on the switch
    Use the 'show version' command or access the Chalet web interface to view the firmware version displayed in the system information or dashboard.
    Affected if The installed version falls within 31.7.0 through 31.7.1.x OR 32.0 through 32.5.1.4.
  2. Confirm Chalet web interface is enabled
    Access the Chalet web application by navigating to the switch's IP address in a browser, or check via CLI for web server status using 'show web' or 'show management' commands.
    Affected if The Chalet web interface is accessible and the switch is managed through it.
  3. Verify the /jsonrpc API endpoint exists
    Attempt to access the /jsonrpc endpoint on the Chalet interface (e.g., https://<switch-ip>/jsonrpc) or inspect network traffic to see if the endpoint responds to requests.
    Affected if The /jsonrpc API responds to requests, indicating it is active.
  4. Check if session tokens include CSRF protection
    Log into the Chalet interface and inspect the HTTP requests/responses for the /jsonrpc API. Look for the presence of anti-CSRF tokens in request headers or parameters.
    Affected if The API requests lack anti-CSRF token validation in headers or body.

A switch is affected if it runs EXOS version 31.7.0-31.7.1.x or 32.0-32.5.1.4, has the Chalet web interface enabled with the /jsonrpc API exposed, and the API lacks CSRF token protection.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 31.7.2 / 32.5.1.5 or later
Fixed in 31.7.232.5.1.5
Interim mitigation

Upgrade EXOS to version 31.7.2 or 32.5.1.5 or later; implement anti-CSRF tokens for API endpoints.

Recommended fix High confidence

EXOS 31.7.2 (for 31.x branch) or EXOS 32.5.1.5 (for 32.x branch)

  1. 1. Inventory all EXOS devices to identify those running affected versions (31.7.0-31.7.1 or 32.0-32.5.1.4)
  2. 2. Determine which EXOS branch (31.x or 32.x) each device is on and plan upgrade accordingly
  3. 3. Download EXOS firmware version 31.7.2 (for 31.x branch) or 32.5.1.5 (for 32.x branch) from Extreme Networks support portal
  4. 4. Schedule a maintenance window to minimize business impact
  5. 5. Back up current configuration of each affected device
  6. 6. Follow Extreme Networks standard firmware upgrade procedures (via console, SSH, or XMC management)
  7. 7. Reboot the device to apply the new firmware
  8. 8. Verify the upgrade was successful by checking the EXOS version (should show 31.7.2 or 32.5.1.5)
Caveat Review Extreme Networks release notes for any compatibility notes or configuration changes between your current version and the target fixed version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Exos Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-43118 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-43118 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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