Cyber Resilience

CVE-2024-42483

Espressif Esp-Now ≤ 2.5.2

Public PoC
Published
12 September 2024
Modified
23 September 2024
Patch / advisory
CVSS Score v3.1 6.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
EPSS Score 0.0030 22th percentile
Risk Priority 49 floored blend · peak EPSS

Summary

CVE-2024-42483 is a medium-severity Acceptance of Extraneous Untrusted Data With Trusted Data (CWE-349) vulnerability in Espressif Esp-Now. Its CVSS base score is 6.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Mark-of-the-Web Bypass (T1553.005); ranked at the 22th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to AC-4 (Information Flow Enforcement) and SC-23 (Session Authenticity) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

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,…

more

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.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1553.005 Mark-of-the-Web Bypass Defense Impairment
Adversaries may abuse specific file formats to subvert Mark-of-the-Web (MOTW) controls.
T1195 Supply Chain Compromise Initial Access
Adversaries may manipulate products or product delivery mechanisms prior to receipt by a final consumer for the purpose of data or system compromise.
T1195.001 Compromise Software Dependencies and Development Tools Initial Access
Adversaries may manipulate software dependencies and development tools prior to receipt by a final consumer for the purpose of data or system compromise.
T1195.002 Compromise Software Supply Chain Initial Access
Adversaries may manipulate application software prior to receipt by a final consumer for the purpose of data or system compromise.
T1542.002 Component Firmware Stealth
Adversaries may modify component firmware to persist on systems.
T1553 Subvert Trust Controls Defense Impairment
Adversaries may undermine security controls that will either warn users of untrusted activity or prevent execution of untrusted programs.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-3749Shared CWE-345, CWE-349
CVE-2026-1642Shared CWE-345, CWE-349
CVE-2023-5548Shared CWE-345, CWE-349
CVE-2024-25638Shared CWE-345, CWE-349
CVE-2025-29842Shared CWE-345, CWE-349
CVE-2023-51655Shared CWE-345, CWE-349
CVE-2025-27840Same vendor: Espressif
CVE-2026-25508Same vendor: Espressif
CVE-2026-46532Same vendor: Espressif
CVE-2025-66409Same vendor: Espressif

Affected Assets

espressif
esp-now
≤ 2.5.2

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)
  • 13 hardening rules · 6 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V1.2.2
  • V10.4.7
  • V3.5.5
  • V3.7.3

Mitigating Controls (NIST 800-53 r5) AI

Explicit requirement to protect session authenticity structurally prevents the weakness for communications.

Information flow enforcement can block untrusted data from being accepted or processed as if it were trusted.

Input validation directly stops acceptance of untrusted data mixed into trusted inputs.

Integrity verification tools detect (but do not stop) the acceptance of data lacking authenticity.

Cryptographic mechanisms can be used to verify authenticity, thereby preventing acceptance of invalid data.

Associating security attributes with data allows the system to distinguish and reject extraneous untrusted portions.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly address proper trust-boundary enforcement and input validation, preventing this class of weakness during development.

RC.RP-05 mostly match
degrades

CWE-345 directly impairs RC.RP-05's verification of restored-asset integrity/authenticity, largely defeating the outcome while still leaving other restoration-confirmation steps partially viable.

PR.DS-01 partial match
prevents

Cryptographic integrity checks on data-at-rest can detect tampering or substitution of untrusted content mixed with trusted data.

PR.DS-02 partial match
prevents

Cryptographic integrity mechanisms on data-in-transit can prevent acceptance of extraneous untrusted data by validating origin and detecting modification.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing can detect the weakness but does not itself implement preventive controls.

mitigates

Network controls can enforce authenticated channels, reducing risk of accepting unauthentic data.

mitigates

Secure network services often include authenticity checks for data exchanged over those services.

prevents

Cryptographic mechanisms directly verify data origin and integrity, preventing acceptance of unauthentic data.

prevents

Secure development lifecycle mandates input validation and trust-boundary enforcement that directly prevents acceptance of untrusted data alongside trusted data.

prevents

Application security requirements explicitly call for strict separation and validation of trusted versus untrusted data sources.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).

Oracle Linux 8 (2 rules)
  • V-248574 YUM must be configured to prevent the installation of patches, service packs, device drivers, or OL 8 system components that have not been digitally signed using a certificate that is recognized and approved by the organization. prevents CWE-345, CWE-349
  • V-248575 OL 8 must prevent the installation of software, patches, service packs, device drivers, or operating system components of local packages without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. prevents CWE-345
Oracle Linux 9 (1 rule)
  • V-271525 OL 9 must have GPG signature verification enabled for all software repositories. prevents CWE-345
RHEL 7 (2 rules)
  • V-204447 The Red Hat Enterprise Linux operating system must prevent the installation of software, patches, service packs, device drivers, or operating system components from a repository without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. prevents CWE-345
  • V-204448 The Red Hat Enterprise Linux operating system must prevent the installation of software, patches, service packs, device drivers, or operating system components of local packages without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. prevents CWE-345
RHEL 8 (2 rules)
  • V-230264 RHEL 8 must prevent the installation of software, patches, service packs, device drivers, or operating system components from a repository without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. prevents CWE-345
  • V-230265 RHEL 8 must prevent the installation of software, patches, service packs, device drivers, or operating system components of local packages without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. prevents CWE-345
RHEL 9 (1 rule)
  • V-257822 RHEL 9 must have GPG signature verification enabled for all software repositories. prevents CWE-345

References