Cyber Resilience

CVE-2024-23973

Memory Safety in Silabs Gecko Os

Memory Safety
Published
31 January 2025
Modified
30 September 2025
CVSS Score v3.1 8.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0052 42th percentile
Risk Priority 64 floored blend · peak EPSS

Summary

CVE-2024-23973 is a high-severity Classic Buffer Overflow (CWE-120) vulnerability in Silabs Gecko Os. Its CVSS base score is 8.8 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 42th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2024-23973 is a stack-based buffer overflow vulnerability (CWE-120) in Silicon Labs Gecko OS, stemming from inadequate validation of the length of user-supplied data in HTTP GET request handling before copying it to a stack-based buffer. This flaw affects installations of the Gecko OS, enabling network-adjacent attackers to execute arbitrary code in the context of the device without requiring authentication. The vulnerability carries a CVSS v3.1 base score of 8.8 (AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), indicating high severity due to its potential for confidentiality, integrity, and availability impacts.

Network-adjacent attackers, positioned on the same local network segment as the affected device, can exploit this vulnerability by sending crafted HTTP GET requests. No privileges or user interaction are needed, allowing low-complexity exploitation that grants remote code execution on the device itself.

Silicon Labs and Zero Day Initiative have published advisories detailing the issue, available at https://community.silabs.com/a45Vm0000000Atp and https://www.zerodayinitiative.com/advisories/ZDI-24-873/, respectively, which security practitioners should consult for patch information and mitigation guidance.

EU & UK References

Vulnerability Data

This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of Silicon Labs Gecko OS. Authentication is not required to exploit this vulnerability. The specific flaw exists within the handling of HTTP GET requests. The issue results from…

more

the lack of proper validation of the length of user-supplied data prior to copying it to a stack-based buffer. An attacker can leverage this vulnerability to execute code in the context of the device.

CWE(s)
CWE-120

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-24731Same product: Silabs Gecko Os
CVE-2025-2837Same product: Silabs Gecko Os
CVE-2024-23938Same product: Silabs Gecko Os
CVE-2024-23937Same product: Silabs Gecko Os
CVE-2025-2838Same product: Silabs Gecko Os
CVE-2023-2686Same vendor: Silabs
CVE-2023-0970Same vendor: Silabs
CVE-2023-41093Same vendor: Silabs
CVE-2026-47154Same vendor: Silabs
CVE-2026-4526Same vendor: Silabs

Affected Assets

silabs
gecko os
all versions

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V5.2.1

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and analysis can find missing size checks before deployment.

SI-10 Information Input Validation good match

Input validation directly enforces size checks before buffer copies.

SA-8 Security and Privacy Engineering Principles partial match

Engineering principles require bounds checking and safe buffer handling in design.

SI-16 Memory Protection partial match

Memory protection limits the impact of an overflow once it occurs.

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 development practices directly enforce bounds checking and input validation that prevent classic buffer overflows.

ID.RA-01 partial match
prevents

Vulnerability identification processes such as code review or scanning detect classic buffer overflows before exploitation.

PR.PS-02 partial match
prevents

Routine patching replaces vulnerable code containing unchecked buffer copies with corrected versions.

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.

A.8.28 Secure coding mostly match
prevents

Secure coding directly requires bounds-checked memory operations, addressing the root cause of CWE-120.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development and acceptance can detect buffer overflows through fuzzing and static analysis, though it does not prevent them at the source.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle mandates processes that can include input validation and bounds checking to prevent buffer overflows.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify input-size validation and safe buffer handling to mitigate classic buffer overflows.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure system architecture and engineering principles promote defensive coding patterns that reduce the likelihood of unchecked buffer copies.

References