dbcve.org
AndroidOperating system · Google

CVE-2022-23425

CRITICAL · 9.8 CVSS v3.1 Published 2022-02-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/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
Improper input validation in Exynos baseband prior to SMR Feb-2022 Release 1 allows attackers to send arbitrary NAS signaling messages with fake base station.

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 baseband processor allows an attacker with a fake base station to send arbitrary NAS (Non-Access Stratum) signaling messages to vulnerable devices. This critical flaw in the cellular baseband firmware enables potential man-in-the-middle attacks, service disruption, or further exploitation of the baseband processor.

MitigationApply the Samsung SMR (Security Maintenance Release) Feb-2022 or later, which contains the patched baseband firmware for Exynos chipsets. Users should ensure their devices receive and install运营商 (carrier) and OEM firmware updates promptly.

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:= 10.0= 11.0= 12.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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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

  1. Confirm device uses Exynos chipset
    Check device specifications or run 'getprop ro.hardware' or 'getprop ro.chipset' in ADB shell to identify the chipset. Exynos variants typically show 'exynos' in the hardware property.
    Affected if Device does not use an Exynos-based baseband processor (this CVE affects only Exynos modems).
  2. Verify Android OS version
    Navigate to Settings > About Phone > Android version or run 'getprop ro.build.version.release' in ADB shell.
    Affected if Android version is 10.0, 11.0, or 12.0 (exact versions as listed in affected products).
  3. Check baseband firmware version
    Run 'getprop gsm.version.baseband' or check the baseband version in Settings > About Phone > Baseband version. Compare against the Feb-2022 SMR patched version for your specific Exynos model.
    Affected if Baseband firmware version is older than the Feb-2022 SMR patch or the device has not received the February 2022 security maintenance release.
  4. Verify security patch level
    Check Settings > About Phone > Security patch level or run 'getprop ro.build.version.security_patch' in ADB shell.
    Affected if Security patch level is earlier than February 2022, indicating the baseband fix has not been applied.

Device is affected if it uses an Exynos chipset, runs Android 10.0, 11.0, or 12.0, and has a baseband firmware or security patch level predating the February 2022 SMR.

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 the Samsung SMR (Security Maintenance Release) Feb-2022 or later, which contains the patched baseband firmware for Exynos chipsets. Users should ensure their devices receive and install运营商 (carrier) and OEM firmware updates promptly.

Recommended fix High confidence

SMR (Samsung Monthly Release) February-2022 Release 1 or later

  1. Check the device's current Android Security Patch level in Settings > About Phone > Software Information
  2. Navigate to Settings > Software Update and tap 'Download and Install' to check for available updates
  3. Ensure the device is updated to Samsung Mobile Security Patch Level (SMR) February 2022 Release 1 or later
  4. If no update is available, check with the device carrier or manufacturer for region-specific updates
  5. After update completion, verify the Security Patch Level shows February 2022 or later in Settings > About Phone > Software Information

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

Fix this in Android Scoped from the published advisory
  • Consultation12.0 h
  • Testing4.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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