# CVE-2024-42483: ESP-NOW Replay Attacks Vulnerability

> Attackers can replay captured packets by clearing shared caches, allowing injection of old messages in ESP-NOW communications.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **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:** 12 Sep 2024
- **Updated:** 12 Sep 2024
- **Also known as:** GHSA-wf6q-c2xr-77xj

## What is CVE-2024-42483?

CVE-2024-42483 is a medium-severity vulnerability in espressif esp-now, published on 12 Sep 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

ESP-NOW Component provides a connectionless Wi-Fi communication protocol. An replay attacks vulnerability was discovered in the implementation of the ESP-NOW because the caches is not differentiated by message types, it is a single, shared resource for all kinds of messages, whether they are broadcast or unicast, and regardless of whether they are ciphertext or plaintext. This can result an attacker to clear the cache of its legitimate entries, there by creating an opportunity to re-inject previously captured packets. This vulnerability is fixed in 2.5.2.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity), CWE-349 (Acceptance of Extraneous Untrusted Data With Trusted Data)

## Which versions are affected by CVE-2024-42483?

It affects 1 product.


Products: Espressif Esp-Now.

## How do I fix CVE-2024-42483?

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

## Is CVE-2024-42483 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-42483 and fix it if it is affected.

What it is: CVE-2024-42483 is a medium-severity vulnerability in espressif esp-now, published on 12 Sep 2024. 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-2024-42483 in the wild and no public exploit code.

Affected product: espressif esp-now. 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-2024-42483/ (Markdown: https://insights.sbomify.com/CVE-2024-42483/index.md)
```

## Sources

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

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