CVE-2023-3487
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 · uneditedAn integer overflow in Silicon Labs Gecko Bootloader version 4.3.1 and earlier allows unbounded memory access when reading from or writing to storage slots.
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 confidenceAn integer overflow in Silicon Labs Gecko Bootloader versions 4.3.1 and earlier allows unbounded memory access when reading from or writing to storage slots, potentially enabling arbitrary code execution or data corruption by overflowing integer values used in memory offset calculations.
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.3.1CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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.
-
Identify if Gecko Bootloader is in useExamine the target device firmware or system information to confirm Silicon Labs Gecko Bootloader is present. Check boot logs, firmware headers, or bootloader identification strings for 'Gecko Bootloader' or 'Silicon Labs' bootloader signatures.Affected if Gecko Bootloader is not present on the device
-
Determine installed bootloader versionRetrieve the bootloader version string from the device. This may be visible in boot logs, bootloader configuration files, firmware metadata, or via diagnostic interfaces such as UART debug output during boot. Look for version numbering in format such as '4.x.x'.Affected if The installed version cannot be determined or is not visible
-
Compare version against affected rangeCompare the identified bootloader version number to the affected range. Versions 4.3.1 and earlier are vulnerable. Versions 4.3.2 and later are patched.Affected if Installed version is 4.3.1 or earlier
-
Check if storage slot feature is enabledExamine the bootloader configuration or firmware to determine if storage slot read/write functionality is actively used. Review bootloader configuration files (such as bootloader-config.h or similar), memory layout definitions, and verify whether storage slot access APIs are being called in the deployed firmware.Affected if Storage slot feature is enabled and actively used in the firmware
A device is affected if it runs Silicon Labs Gecko Bootloader version 4.3.1 or earlier and utilizes the storage slot feature for memory operations.
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 Gecko Bootloader to version 4.3.2 or later to obtain the vendor patch; verify deployed devices are running the patched bootloader version and consider firmware integrity verification mechanisms.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,192.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-3487 — 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-3487 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