CVE-2023-35649
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 · uneditedIn several functions of Exynos modem files, there is a possible out of bounds write due to a missing bounds check. This could lead to remote code execution with System execution privileges needed. User interaction is not needed for exploitation.
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 confidenceA missing bounds check in multiple functions of the Exynos modem firmware allows an out-of-bounds write, which can be exploited for remote code execution. The attack requires System-level privileges but needs no user interaction.
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 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
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 Exynos modem presenceCheck device information for Exynos chipset or baseband/modem version details. On Android, go to Settings > About Phone > Baseband version or use 'getprop' commands to inspect radio-related properties (e.g., gsm.version.baseband, ril.model).Affected if Device runs Exynos modem firmware
-
Determine modem firmware versionRetrieve the baseband/modem firmware version from the device. Use 'getprop | grep baseband' or check Settings > About Phone > Baseband version. Note the full version string.Affected if Baseband version matches known vulnerable Exynos firmware builds
-
Verify Android system versionCheck the Android OS version in Settings > About Phone > Android version. Note that exploitation requires system-level privileges on the device.Affected if Device runs any Android version with vulnerable Exynos modem
-
Confirm system privileges existReview whether the device has been compromised or has apps with elevated/system privileges. Check for unauthorized root access or suspicious system-level modifications.Affected if Attacker gains system-level privileges on affected device
User is affected if their Android device uses Exynos modem firmware with the missing bounds check vulnerability and the attacker has achieved system-level privileges.
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.
dbcve · scopedApply Samsung's security updates for affected Exynos modem devices; organizations should identify and patch all devices running vulnerable Exynos modem firmware versions.
Android security patch level November 2023 or later (2023-11-01)
- Check the current Android security patch level on the device in Settings > About Phone > Security Patch Level
- Apply the latest Android security update available for your device. For most devices, this means updating to the November 2023 security patch level or later
- If your device manufacturer has released a specific update addressing CVE-2023-35649, ensure that update is installed
- Verify the security patch level has been updated after applying the fix
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-35649 — 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-35649 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