Iq EngineOperating system · Extremenetworks

CVE-2023-35803

CRITICAL · 9.8 CVSS v3.1 Published 2023-10-04
Fix available
A fix is available. Upgrade to 10.6r2 / 10.6r5 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
IQ Engine before 10.6r2 on Extreme Network AP devices has a Buffer Overflow.

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

A buffer overflow vulnerability exists in IQ Engine (wireless management software) on Extreme Networks access point devices in versions prior to 10.6r2. This memory corruption flaw could allow remote attackers to execute arbitrary code or cause denial of service due to improper bounds checking when processing input.

MitigationUpgrade IQ Engine to version 10.6r2 or later. If immediate patching is not possible, restrict network access to management interfaces and implement compensating controls such as network segmentation.

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
Iq EngineOperating system
Affected:< 10.6r2< 10.6r5

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

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

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

  1. Identify the device model and product
    Access the device CLI or management interface and run commands to display the hardware model and software version. For Extreme Networks access points, common commands include 'show version' or 'get version' in the IQ Engine CLI.
    Affected if The device is an Extreme Networks access point running IQ Engine software
  2. Determine the IQ Engine version
    In the IQ Engine CLI or management interface, look for version information typically displayed by 'show version' or 'get system-info'. Locate the firmware/software version number.
    Affected if The displayed IQ Engine version is below 10.6r2 or below 10.6r5 (both ranges indicate vulnerability)
  3. Verify management interface accessibility
    Check network configuration to determine if the IQ Engine management interface (typically ports 443 or 80 for web, or SSH for CLI) is accessible from untrusted networks. Review access control lists or firewall rules.
    Affected if The management interface is exposed to untrusted networks without proper network segmentation or ACLs
  4. Confirm IQ Engine web service is running
    Attempt to access the IQ Engine web interface via HTTPS or HTTP to the access point IP address, or check running services via CLI command such as 'show services' or similar.
    Affected if The IQ Engine management web service is enabled and responding

The environment is affected if the Extreme Networks access point runs IQ Engine version below 10.6r2 or below 10.6r5 and has the management interface accessible.

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 10.6r2 / 10.6r5 or later
Fixed in 10.6r210.6r5
Interim mitigation

Upgrade IQ Engine to version 10.6r2 or later. If immediate patching is not possible, restrict network access to management interfaces and implement compensating controls such as network segmentation.

Recommended fix Moderate confidence

IQ Engine 10.6r2 or later

  1. Identify all affected Extreme Network AP devices running IQ Engine versions before 10.6r2
  2. Access the AP device management interface or CLI
  3. Download IQ Engine version 10.6r2 or later from Extreme Networks support portal
  4. Upload the firmware to the AP device or controller
  5. Initiate the firmware upgrade process
  6. Verify the upgrade completed successfully by checking the IQ Engine version
  7. Confirm the device is functioning normally post-upgrade

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

Fix this in Iq Engine Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-35803 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-35803 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