# CVE-2023-35802: Memory corruption in n/a

> A buffer overflow in the CAPWAP protocol allows remote code execution and privilege escalation on Extreme Networks AP devices, requiring internal network access.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jul 2023
- **Updated:** 30 Oct 2024
- **Also known as:** GHSA-26p5-j42v-vp3h

## What is CVE-2023-35802?

CVE-2023-35802 is a critical memory corruption vulnerability in n/a, published on 15 Jul 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

IQ Engine before 10.6r1 on Extreme Network AP devices has a Buffer Overflow in the implementation of the CAPWAP protocol that may be exploited to obtain elevated privileges to conduct remote code execution. Access to the internal management interface/subnet is required to conduct the exploit.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2023-35802?

It affects 1 product.


Products: Extremenetworks Iq Engine.

## How do I fix CVE-2023-35802?

No fix has been published for CVE-2023-35802 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-35802 being exploited?

There is no known exploitation of CVE-2023-35802 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2023-35803](https://insights.sbomify.com/CVE-2023-35803/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-35802 and fix it if it is affected.

What it is: CVE-2023-35802 is a critical memory corruption vulnerability in n/a, published on 15 Jul 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-35802 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-35802/ (Markdown: https://insights.sbomify.com/CVE-2023-35802/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-35802
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-35802
- OSV: https://osv.dev/vulnerability/CVE-2023-35802

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-35802/
Summaries are generated and may contain mistakes; the official description above is the record.