# CVE-2023-41821: Information disclosure in Phones

> A local attacker can read sensitive user information via an improper export vulnerability in the Motorola Setup application.

- **Severity:** Medium 5.0 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N`)
- **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:** 3 May 2024
- **Updated:** 23 Aug 2024
- **Also known as:** GHSA-p54x-grmr-9gw6

## What is CVE-2023-41821?

CVE-2023-41821 is a medium-severity vulnerability in Motorola Phones, published on 3 May 2024. 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

A an improper export vulnerability was reported in the Motorola Setup application that could allow a local attacker to read sensitive user information.

Weakness: CWE-926 (Improper Export of Android Application Components)

## Which versions are affected by CVE-2023-41821?


## How do I fix CVE-2023-41821?

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

## Is CVE-2023-41821 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-41821 and fix it if it is affected.

What it is: CVE-2023-41821 is a medium-severity vulnerability in Motorola Phones, published on 3 May 2024. 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-2023-41821 in the wild and no public exploit code.

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

## Sources

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

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