# CVE-2025-20902: Missing authorization in Media Controller

> A local attacker can launch activities with elevated privileges due to improper access control in the Samsung Media Controller application.

- **Severity:** Medium 5.1 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/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:** No
- **Published:** 4 Feb 2025
- **Updated:** 4 Feb 2025
- **Also known as:** GHSA-34g6-cvrg-j3q3

## What is CVE-2025-20902?

CVE-2025-20902 is a medium-severity missing authorization vulnerability in Samsung Mobile Media Controller, published on 4 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper access control in Media Controller prior to version 1.0.24.5282 allows local attacker to launch activities in MediaController's privilege.

## Which versions are affected by CVE-2025-20902?


## How do I fix CVE-2025-20902?

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

## Is CVE-2025-20902 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-20902 and fix it if it is affected.

What it is: CVE-2025-20902 is a medium-severity missing authorization vulnerability in Samsung Mobile Media Controller, published on 4 Feb 2025. 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-2025-20902 in the wild and no public exploit code.

Affected product: Samsung Mobile Media Controller. 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-2025-20902/ (Markdown: https://insights.sbomify.com/CVE-2025-20902/index.md)
```

## Sources

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

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