# CVE-2018-5787: Memory corruption in n/a

> Remote unauthenticated attackers can trigger a stack overflow in the RIM process via crafted packets, potentially leading to code execution or denial of service on ExtremeWireless Access Points.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** 5 Feb 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-7v73-phx5-xfvv

## What is CVE-2018-5787?

CVE-2018-5787 is a high-severity memory corruption vulnerability in n/a, published on 5 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in Extreme Networks ExtremeWireless WiNG 5.x before 5.8.6.9 and 5.9.x before 5.9.1.3. There is a Remote, Unauthenticated Stack Overflow in the RIM (Radio Interface Module) process running on the WiNG Access Point via crafted packets.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2018-5787?

It affects 1 product.


Products: Extremenetworks Extremewireless Wing.

## How do I fix CVE-2018-5787?

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

## Is CVE-2018-5787 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-5797](https://insights.sbomify.com/CVE-2018-5797/): Hardcoded credentials in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-5787 and fix it if it is affected.

What it is: CVE-2018-5787 is a high-severity memory corruption vulnerability in n/a, published on 5 Feb 2018. 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-2018-5787 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-2018-5787/ (Markdown: https://insights.sbomify.com/CVE-2018-5787/index.md)
```

## Sources

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

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