dbcve.org
AndroidOperating system · Samsung

CVE-2023-21472

MEDIUM · 6.8 CVSS v3.1 Published 2025-09-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated

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
Improper input validation with Exynos Fastboot USB Interface prior to SMR Apr-2023 Release 1 allows a physical attacker to execute arbitrary code in bootloader.

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 confidence

Improper input validation in the Exynos Fastboot USB interface allows a physically proximate attacker to send specially crafted USB commands that bypass validation checks and execute arbitrary code within the bootloader context, achieving code execution at a highly privileged level.

MitigationApply Samsung's SMR (Security Maintenance Release) April 2023 or later, which contains the fix for the improper input validation vulnerability in the Exynos Fastboot USB bootloader component.

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
AndroidOperating system
Affected:= 11.0= 12.0= 13.0

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
Physical
Complexity
High
Privileges
High
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:P/AC:H/PR:H/UI:R/S:C/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 chipset
    Check if the device uses an Exynos processor. On most devices, this can be found in Settings > About Phone > Processor or by checking the device model number against Samsung's specifications. Exynos variants are typically sold in certain regions (Europe, Middle East, Africa) while Snapdragon variants are sold in others (US, China).
    Affected if The device uses an Exynos chipset (the vulnerability only affects Exynos-based devices)
  2. Check the Android version
    Navigate to Settings > About Phone > Android Version, or run 'adb shell getprop ro.build.version.release' via USB debugging.
    Affected if The Android version is exactly 11.0, 12.0, or 13.0 (these specific versions are listed as affected)
  3. Verify USB debugging is enabled
    On the device, go to Settings > Developer Options > USB Debugging. If Developer Options is hidden, tap Settings > About Phone > Build Number 7 times to enable it. Alternatively, run 'adb devices' from a computer to see if the device is authorized for debugging.
    Affected if USB debugging is enabled (this provides the attack vector for sending crafted USB commands)
  4. Check fastboot/bootloader accessibility
    Power off the device, then hold Volume Down + Power to enter download mode, or connect the device to a computer and run 'fastboot devices' to see if the device responds in fastboot mode.
    Affected if Fastboot mode is accessible and the device responds (the vulnerability is in the Exynos Fastboot USB bootloader interface)
  5. Confirm bootloader lock status
    In fastboot mode, run 'fastboot oem device-info' to check if the bootloader is locked or unlocked. The 'Device unlocked' field will show yes or no.
    Affected if Bootloader is unlocked or fastboot commands can be executed without restriction

A user is affected if they have an Exynos-based Samsung device running Android 11.0, 12.0, or 13.0 with USB debugging or fastboot accessible, as the improper input validation in the Exynos Fastboot USB bootloader allows code execution when crafted USB commands are sent.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Samsung's SMR (Security Maintenance Release) April 2023 or later, which contains the fix for the improper input validation vulnerability in the Exynos Fastboot USB bootloader component.

Recommended fix High confidence

SMR Apr-2023 Release 1 (or later)

  1. Check for system software updates on the Samsung device
  2. Navigate to Settings > Software update > Download and install
  3. Ensure the device updates to the SMR (Security Maintenance Release) April 2023 or later
  4. Verify the patch level after update: Settings > About phone > Software information > Security patch level should show April 2023 or later

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Android Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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