CVE-2023-2686
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedBuffer overflow in Wi-Fi Commissioning MicriumOS example in Silicon Labs Gecko SDK v4.2.3 or earlier allows connected device to write payload onto the stack.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceStack-based buffer overflow in the Wi-Fi Commissioning MicriumOS example of Silicon Labs Gecko SDK v4.2.3 and earlier allows a remote, adjacent attacker to write arbitrary payload onto the stack, potentially enabling remote code execution on affected devices.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 4.2.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate the Gecko SDK version in useInspect your project files (e.g., .sls, .gpdk, or manifest files) or check the SDK installation directory for a version.txt or release_notes file. Look for a version field or folder name containing 'Gecko_SDK' followed by a version number.Affected if The SDK version is 4.2.3 or earlier, or the version cannot be determined but is known to be old.
-
Identify if Wi-Fi Commissioning feature is deployedSearch your built firmware image, project source tree, or device documentation for references to 'Wi-Fi Commissioning', 'wifi_commissioning', or the MicriumOS RTOS. Check for inclusion of source files from the Wi-Fi Commissioning example path.Affected if The Wi-Fi Commissioning example code or compiled binary is present in your deployment.
-
Verify MicriumOS is the RTOS in useExamine your project configuration, build scripts, or firmware image for MicriumOS references (e.g., 'micrium', 'uc-os', 'micriumos' in source files, linker scripts, or RTOS configuration). Confirm this RTOS is linked into the final firmware.Affected if MicriumOS is the RTOS compiled into the firmware alongside Wi-Fi Commissioning.
-
Check network exposure of the deviceReview network configuration, firewall rules, or device access controls to determine if the Wi-Fi Commissioning service port/interface is reachable from adjacent network segments or untrusted networks.Affected if The device's Wi-Fi Commissioning service is accessible from remote or adjacent network attackers.
You are affected if your deployed device uses Gecko SDK version 4.2.3 or earlier with the Wi-Fi Commissioning MicriumOS example enabled and that service is network-accessible.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade Silicon Labs Gecko SDK to v4.2.4 or later to obtain the patched version of the Wi-Fi Commissioning example; if upgrading is not immediately feasible, disable or restrict network access to the Wi-Fi Commissioning service.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-2686 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-2686 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data