# CVE-2022-3407: Denial of service in Motorola smartphones

> A modem reset during calls while USB tethering can block emergency service access, requiring a firmware patch for Motorola smartphones.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:P/AC:L/PR:L/UI:R/S:C/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 1 Sep 2023
- **Updated:** 27 Sep 2024
- **Also known as:** GHSA-h364-697w-mgpc

## What is CVE-2022-3407?

CVE-2022-3407 is a medium-severity denial of service vulnerability in Motorola smartphones, published on 1 Sep 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

I some cases, when the device is USB-tethered to a host PC, and the device is sharing its mobile network connection with the host PC, if the user originates a call on the device, then the device's modem may reset and cause the phone call to not succeed.  This may block the user from dialing emergency services.  This patch resolves the device's modem reset issue.

Weakness: CWE-404 (Improper Resource Shutdown or Release)

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

It affects 1 product.


Products: Motorola Smartphone Firmware.

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

No fix has been published for CVE-2022-3407 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-3407 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-3407 is a medium-severity denial of service vulnerability in Motorola smartphones, published on 1 Sep 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-3407 in the wild and no public exploit code.

Affected product: Motorola smartphones. 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-3407/ (Markdown: https://insights.sbomify.com/CVE-2022-3407/index.md)
```

## Sources

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

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