dbcve.org
Exynos 850 FirmwareOperating system · Samsung

CVE-2024-32504

HIGH · 7.8 CVSS v3.1 Published 2024-06-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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
An issue was discovered in Samsung Mobile Processor and Wearable Processor Exynos 850, Exynos 1080, Exynos 2100, Exynos 1280, Exynos 1380, Exynos 1330, Exynos W920, Exynos W930. The mobile processor lacks proper length checking, which can result in an OOB (Out-of-Bounds) Write vulnerability.

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

OOB Write vulnerability in Samsung Exynos mobile and wearable processors (850, 1080, 2100, 1280, 1380, 1330, W920, W930) due to missing length validation checks in firmware. This allows writing data beyond allocated buffer boundaries, potentially enabling privilege escalation or code execution in kernel/privileged context.

MitigationAwait and apply firmware/security patch updates from Samsung and original equipment manufacturers. This is a low-level processor firmware issue requiring vendor-supplied updates; no application-level workarounds available.

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 850 FirmwareOperating system
Affected:all versions
Exynos 1080 FirmwareOperating system
Affected:all versions
Exynos 2100 FirmwareOperating system
Affected:all versions
Exynos 1280 FirmwareOperating system
Affected:all versions
Exynos 1380 FirmwareOperating system
Affected:all versions
Exynos 1330 FirmwareOperating system
Affected:all versions
Exynos W920 FirmwareOperating system
Affected:all versions
Exynos W930 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
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 checks

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

  1. Identify the Exynos processor model
    Check system information via /proc/cpuinfo on Android devices, or use device diagnostic tools (like CPU-Z, AIDA64) or check the device specifications in Settings > About Phone > Processor information. On wearable devices, check through the companion phone app or device settings.
    Affected if The processor model is one of: Exynos 850, 1080, 2100, 1280, 1380, 1330, W920, or W930
  2. Check the baseband processor firmware version
    On Android, dial *#1234# or go to Settings > About Phone > Baseband version to view the modem/baseband firmware version. For wearables, check through the paired phone's Galaxy Wearable app under Device Information > Software version. The baseband version typically contains a string like 'S5E' followed by numbers.
    Affected if The baseband/modem firmware version matches the affected Exynos model (the version string will indicate the chip, e.g., S5E9830 for Exynos 2100) and has not been updated to a patched release
  3. Verify security patch level
    Go to Settings > About Phone > Software Information > Security patch level on Android, or check through the device settings on Tizen-based wearables. Samsung releases monthly security patches that may include firmware fixes for the processor.
    Affected if The Security Patch Level is earlier than the date when Samsung released the fix for this CVE (check Samsung's security bulletins at security.samsungmobile.com)
  4. Check bootloader version and Knox status
    On Samsung devices, boot into download mode (*#9900#) or check Knox status in Settings > Security > Knox. Some firmware vulnerabilities may be mitigated or detectable through Knox attestation if the device has Samsung's security framework.
    Affected if The device shows Knox as tripped or the bootloader is in a debug/development state, indicating potential exposure to firmware-level attacks

A user is affected if their device contains one of the listed Exynos processors (850, 1080, 2100, 1280, 1380, 1330, W920, W930) and the firmware has not been updated to include the security patch for this vulnerability.

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

Await and apply firmware/security patch updates from Samsung and original equipment manufacturers. This is a low-level processor firmware issue requiring vendor-supplied updates; no application-level workarounds available.

Fix this in Exynos 850 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Testing4.0 h
  • Review / QA4.0 h
16.0 hours of engineering $2,920
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-32504 — 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-32504 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