# CVE-2019-12588: The client 802.11 mac implementation in Espressif ESP8266_NONOS_SDK 2.2.0 through 3.1.0 does not validate correctly the RSN AuthKey suite li


- **Severity:** Medium 6.5 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 4 Sep 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-w5cj-7hxw-2355

## What is CVE-2019-12588?

CVE-2019-12588 is a medium-severity vulnerability in n/a, published on 4 Sep 2019. 

### Official description

The client 802.11 mac implementation in Espressif ESP8266_NONOS_SDK 2.2.0 through 3.1.0 does not validate correctly the RSN AuthKey suite list count in beacon frames, probe responses, and association responses, which allows attackers in radio range to cause a denial of service (crash) via a crafted message.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 2 products.


Products: Espressif Arduino Esp8266, Espressif Esp8266 Nonos Sdk.

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

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

## Is CVE-2019-12588 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-12588 is a medium-severity vulnerability in n/a, published on 4 Sep 2019. 
Exploitation: There is no known exploitation of CVE-2019-12588 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-12588/ (Markdown: https://insights.sbomify.com/CVE-2019-12588/index.md)
```

## Sources

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

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