# CVE-2022-30731: Missing authorization in My Files

> Attackers can access arbitrary private files in the Samsung My Files application due to improper access control.

- **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:** 7 Jun 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-4x8q-m44c-w3xc

## What is CVE-2022-30731?

CVE-2022-30731 is a medium-severity missing authorization vulnerability in Samsung Mobile My Files, published on 7 Jun 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper access control vulnerability in My Files prior to version 13.1.00.193 allows attackers to access arbitrary private files in My Files application.

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Samsung My Files.

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

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

## Is CVE-2022-30731 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-30731 is a medium-severity missing authorization vulnerability in Samsung Mobile My Files, published on 7 Jun 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-30731 in the wild and no public exploit code.

Affected product: Samsung Mobile My Files. 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-30731/ (Markdown: https://insights.sbomify.com/CVE-2022-30731/index.md)
```

## Sources

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

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