CVE-2022-39902
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 · uneditedImproper authorization in Exynos baseband prior to SMR DEC-2022 Release 1 allows remote attacker to get sensitive information including IMEI via emergency call.
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 confidenceThis is an improper authorization vulnerability in Samsung Exynos baseband firmware. The issue allows a remote attacker to bypass authorization checks in the emergency call functionality, enabling access to sensitive device identifiers such as the IMEI without proper authentication.
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 dataall versionsCVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Samsung devices with Exynos chipsetsInventory mobile devices to determine chipset type - on Android devices, this can be found in Settings > About Phone > Chipset or through MDM inventory scripts (e.g., 'getprop' command showing 'exynos' in build info)Affected if Device uses Samsung Exynosbaseband processor and is running pre-patch firmware
-
Check Android security patch levelOn the device, go to Settings > About Phone > Security Patch Level, or use MDM to query android.os.Build.VERSION.SECURITY_PATCHAffected if Security Patch Level is earlier than December 2022 (DEC-2022) or shows no patch date
-
Verify baseband firmware versionOn Android, dial *#0011# or use *#*#197328640#*#* to access service mode, or run 'getprop gsm.version.baseband' via ADBAffected if Baseband version cannot be verified or is from before December 2022 SMR release
-
Confirm emergency call functionality accessibilityAttempt to access emergency dialer (dial 112 or local emergency number) and verify if it can be reached without triggering normal authenticationAffected if Emergency dialer is accessible and returns device identifiers (IMEI) without PIN/pattern/password challenge
User is affected if they have a Samsung device with Exynos chipset running firmware without the December 2022 security patch, where the emergency call function exposes IMEI without authentication.
Generated from the published advisory. Verify against your own configuration.
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 · scopedApply the Samsung SMR DEC-2022 Release 1 or later security patch to affected devices. Organizations should inventory Samsung devices using Exynos chipsets and ensure firmware updates are deployed through MDM or manual update processes.
SMR DEC-2022 Release 1 or later
- Check current SMR (Security Maintenance Release) version on the device via Settings > Security > Security update
- Ensure the device is updated to SMR DEC-2022 Release 1 or later to receive the fix for this vulnerability
- For affected Exynos-based Samsung devices, apply the latest available security update from Samsung
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing4.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,280.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-39902 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-39902 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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