dbcve.org
Exynos 9820 FirmwareOperating system · Samsung

CVE-2023-50804

MEDIUM · 5.3 CVSS v3.1 Published 2024-06-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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
An issue was discovered in Samsung Mobile Processor, and Modem Exynos 9820, Exynos 9825, Exynos 980, Exynos 990, Exynos 850, Exynos 1080, Exynos 2100, Exynos 2200, Exynos 1280, Exynos 1380, Exynos 1330, Exynos Modem 5123, Exynos Modem 5300. The baseband software does not properly check format types specified by the NAS (Non-Access-Stratum) module. This can lead to bypass of authentication.

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 exists in Samsung Exynos baseband/modem firmware where the NAS (Non-Access-Stratum) module's format type validation is insufficient. The improper checking of format types allows an attacker to potentially bypass authentication mechanisms in the cellular protocol stack.

MitigationApply vendor-supplied firmware updates for affected Exynos processors and modems. Since this is a baseband firmware issue, end users should ensure their devices receive运营商 (carrier) and Samsung security updates. No user-configurable mitigation is 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 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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

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 in your device
    Check your device specifications or system information to determine if the device uses an Exynos chipset (9820, 9825, 980, 990, 850, 1080, 2100, or 2200). This information is typically found in Settings > About Phone or through device diagnostic tools.
    Affected if The device contains any of the listed Exynos processors (9820, 9825, 980, 990, 850, 1080, 2100, 2200)
  2. Check the baseband/modem firmware version
    Access the baseband firmware version through your device's settings (Settings > About Phone > Baseband version) or by entering Samsung's engineering diagnostic code (*#0*# or *#1234*#). Record the firmware version string.
    Affected if The baseband firmware version corresponds to any version on an affected Exynos processor (all versions are vulnerable)
  3. Verify security update status
    Check when your device last received a security update by going to Settings > Software Update > Security Patch Level. Note the date of the installed security update.
    Affected if The device has not received security updates that address CVE-2023-50804 (contact your carrier or Samsung for specific patch dates)
  4. Confirm the NAS module is in use
    This vulnerability exists in the NAS (Non-Access-Stratum) module of the baseband firmware. This module is always active during cellular communication on affected devices, as it handles control plane procedures including authentication.
    Affected if The device uses cellular network services (2G/3G/4G/5G) on an affected Exynos baseband

If your Samsung device uses any of the affected Exynos processors (9820, 9825, 980, 990, 850, 1080, 2100, 2200) and has not received vendor-supplied firmware updates addressing CVE-2023-50804, you are affected by this vulnerability in the NAS module's format type validation.

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-supplied firmware updates for affected Exynos processors and modems. Since this is a baseband firmware issue, end users should ensure their devices receive运营商 (carrier) and Samsung security updates. No user-configurable mitigation is available.

Fix this in Exynos 9820 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation20.0 h
  • Testing16.0 h
  • Review / QA8.0 h
50.0 hours of engineering $8,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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