CVE-2023-50806
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 · uneditedA vulnerability was discovered in Samsung Mobile Processor, Wearable Processor, and Modems with versions Exynos 9820, Exynos 9825, Exynos 980, Exynos 990, Exynos 850 Exynos 1080, Exynos 2100, Exynos 2200, Exynos 1280, Exynos 1380 Exynos 1330, Exynos 9110, Exynos W920, Exynos W930, Exynos Modem 5123, Exynos Modem 5300 that allows out-of-bounds access to a heap buffer in the SIM Proactive Command.
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 · high confidenceOut-of-bounds heap buffer access vulnerability in the SIM Proactive Command handler across Samsung Exynos mobile processors, wearable processors, and modems allows memory corruption that could enable arbitrary code execution or denial of service via malicious SIM commands.
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 dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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.
-
Identify the Exynos chip model in your deviceCheck device specifications, kernel logs, or modem firmware identification (e.g., AT command responses, boot logs, /proc/cpuinfo on rooted devices)Affected if The chip model is one of: Exynos Modem 5123, Modem 5300, 9820, 9825, 980, 990, 850, or 1080
-
Determine the firmware version of the affected Exynos componentQuery the modem firmware version through manufacturer diagnostic tools, AT commands (e.g., AT+CGMR), or system information on rooted devicesAffected if The firmware version is any version (all versions are affected for listed chips)
-
Verify SIM functionality is present and enabledConfirm the device has SIM card capability and the SIM Proactive Command handler is active (this is typically enabled by default on any device with a SIM slot)Affected if The device supports and uses SIM cards with the Exynos modem/processor
-
Check the baseband/modem security patch levelLook for baseband or modem security patch information in system settings, about phone, or through diagnostic interfaces (if available)Affected if The security patch level is earlier than the vendor-supplied fix date for CVE-2023-50806
Your device is affected if it contains any of the listed Exynos chips (Modem 5123, Modem 5300, 9820, 9825, 980, 990, 850, or 1080) and uses SIM functionality, since all firmware versions of these components are vulnerable.
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 dataApply vendor-supplied firmware/security patch updates from Samsung for affected devices; coordinate with device manufacturers for embedded systems using these chips.
- Consultation16.0 h
- Implementation8.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,608.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-50806 — 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-50806 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