# CVE-2022-39901: Auth bypass in Samsung Mobile Devices

> Remote attackers can disable network traffic encryption between the device and base station due to improper authentication in the Exynos baseband.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Dec 2022
- **Updated:** 23 Apr 2025
- **Also known as:** A-263783333, GHSA-cgvm-v5x3-2hm9, PUB-A-263783333

## What is CVE-2022-39901?

CVE-2022-39901 is a medium-severity authentication bypass vulnerability in Samsung Mobile Devices, published on 8 Dec 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper authentication in Exynos baseband prior to SMR DEC-2022 Release 1 allows remote attacker to disable the network traffic encryption between UE and gNodeB.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2022-39901?

It affects 1 product.


Products: Samsung Exynos Firmware.

## How do I fix CVE-2022-39901?

Apply the vendor's patch.

## Is CVE-2022-39901 being exploited?

There is no known exploitation of CVE-2022-39901 in the wild and no public exploit code.

## Other vulnerabilities in Samsung Mobile Devices

- [CVE-2022-39902](https://insights.sbomify.com/CVE-2022-39902/): Information disclosure in Samsung Mobile Devices (medium 6.5)
- [CVE-2023-21455](https://insights.sbomify.com/CVE-2023-21455/): Auth bypass in Samsung Mobile Devices (medium 5.9)
- [CVE-2022-39881](https://insights.sbomify.com/CVE-2022-39881/): Information disclosure in Samsung Mobile Devices (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-39901 and fix it if it is affected.

What it is: CVE-2022-39901 is a medium-severity authentication bypass vulnerability in Samsung Mobile Devices, published on 8 Dec 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-39901 in the wild and no public exploit code.

Affected product: Samsung Mobile Devices. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-39901/ (Markdown: https://insights.sbomify.com/CVE-2022-39901/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-39901
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-39901
- OSV: https://osv.dev/vulnerability/CVE-2022-39901

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-39901/
Summaries are generated and may contain mistakes; the official description above is the record.