Remote memory corruption via unchecked payload copy
Published Jun 15, 2023 · Updated Dec 12, 2024
Stack buffer overflow in Silicon Labs Gecko SDK 4.2.3 and earlier allows remote attackers to corrupt memory through its MicriumOS Wi-Fi example. The MicriumOS example copies a connected device's payload into a stack buffer without checking that the input fits the destination. The example must be compiled into device firmware and exposed to a connected peer; public sources do not identify the affected function or a deterministic outcome beyond stack overwrite.
Summary
What happened
Stack buffer overflow in Silicon Labs Gecko SDK 4.2.3 and earlier allows remote attackers to corrupt memory through its MicriumOS Wi-Fi example. The MicriumOS example copies a connected device's payload into a stack buffer without checking that the input fits the destination. The example must be compiled into device firmware and exposed to a connected peer; public sources do not identify the affected function or a deterministic outcome beyond stack overwrite.
The record
- CVE
- CVE-2023-2686
- Published
- Jun 15, 2023
- Updated
- Dec 12, 2024
- Vendor
- Silicon Laboratories
- Product
- Gecko Platform
- Classifications
- CWE-120
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 15, 2023CVE publishedPublication date reported by the CVE source.
- Dec 12, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=4.2.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo