dbcve.org
Exynos 9820 FirmwareOperating system · Samsung

CVE-2024-29153

HIGH · 8.1 CVSS v3.1 Published 2024-07-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
A 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, and Exynos Modem 5300 that involves incorrect authorization of LTE NAS messages and leads to downgrading to lower network generations and repeated DDOS.

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 confidence

This vulnerability in Samsung Exynos baseband/modem processors (mobile, wearable, and standalone modems) allows incorrect authorization of LTE NAS (Non-Access Stratum) messages. An attacker can exploit this to force devices to downgrade from LTE to lower network generations (3G/2G) and cause repeated denial-of-service conditions through malformed signaling messages.

MitigationApply vendor-provided firmware/security updates from Samsung for affected Exynos processors and modems. Organizations should inventory affected devices and prioritize patching given the high CVSS score and potential for persistent network disruption.

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
Exynos 9820 FirmwareOperating system
Affected:all versions
Exynos 9825 FirmwareOperating system
Affected:all versions
Exynos 980 FirmwareOperating system
Affected:all versions
Exynos 990 FirmwareOperating system
Affected:all versions
Exynos 850 FirmwareOperating system
Affected:all versions
Exynos 1080 FirmwareOperating system
Affected:all versions
Exynos 2100 FirmwareOperating system
Affected:all versions
Exynos 2200 FirmwareOperating system
Affected:all versions

CVSS 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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device processor model
    Check the device settings under 'About Phone' > 'Processor' or 'Chipset' to determine if the device uses a Samsung Exynos processor, or use terminal command: 'cat /proc/cpuinfo' to find the hardware model
    Affected if The device contains any of the following Exynos processors: 9820, 9825, 980, 990, 850, 1080, 2100, or 2200
  2. Check baseband/modem firmware version
    On the device, navigate to Settings > About Phone > Software Information, or dial *#1234# to access the hidden service menu, and locate the 'Baseband' or 'Modem' version entry
    Affected if Any baseband firmware version is present on an affected Exynos processor (all versions are vulnerable)
  3. Verify LTE connectivity is enabled
    Check if the device has LTE/4G network capability by reviewing the cellular network settings under Settings > Mobile Networks > Network Mode, or inspect via: 'getprop ro.telephony.default_network'
    Affected if The device supports and has LTE enabled, as the vulnerability exploits LTE NAS message authorization to force downgrades
  4. Confirm device model is from affected Samsung product line
    Cross-reference the device model number (found in Settings > About Phone > Model Number) against Samsung's product database for phones, wearables, or standalone modems containing the affected Exynos chipsets
    Affected if The device is a Samsung mobile phone, wearable, or standalone modem using one of the listed Exynos processors

The environment is affected if any device contains one of the listed Exynos processors (9820, 9825, 980, 990, 850, 1080, 2100, 2200) with LTE capability enabled, regardless of baseband firmware version.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-provided firmware/security updates from Samsung for affected Exynos processors and modems. Organizations should inventory affected devices and prioritize patching given the high CVSS score and potential for persistent network disruption.

Fix this in Exynos 9820 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-29153 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-29153 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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