# CVE-2019-6496: Memory corruption in n/a

> Remote attackers can execute arbitrary code or cause denial of service on Marvell Avastar Wi-Fi devices via malformed packets during network scanning.

- **Severity:** High 8.8 (`CVSS:3.0/AV:A/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jan 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-vx6q-ffvw-7c86

## What is CVE-2019-6496?

CVE-2019-6496 is a high-severity memory corruption vulnerability in n/a, published on 19 Jan 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The ThreadX-based firmware on Marvell Avastar Wi-Fi devices, models 88W8787, 88W8797, 88W8801, 88W8897, and 88W8997, allows remote attackers to execute arbitrary code or cause a denial of service (block pool overflow) via malformed Wi-Fi packets during identification of available Wi-Fi networks. Exploitation of the Wi-Fi device can lead to exploitation of the host application processor in some cases, but this depends on several factors including host OS hardening and the availability of DMA.

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

## Which versions are affected by CVE-2019-6496?

It affects 5 products.


Products: Marvell 88w8787 Firmware, Marvell 88w8797 Firmware, Marvell 88w8801 Firmware, Marvell 88w8897 Firmware, Marvell 88w8997 Firmware.

## How do I fix CVE-2019-6496?

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

## Is CVE-2019-6496 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-6496 and fix it if it is affected.

What it is: CVE-2019-6496 is a high-severity memory corruption vulnerability in n/a, published on 19 Jan 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-6496 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-2019-6496/ (Markdown: https://insights.sbomify.com/CVE-2019-6496/index.md)
```

## Sources

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

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