# CVE-2022-30745: Improper access control vulnerability in Quick Share prior to version 13.1.2.4 allows attacker to access internal files in Quick Share.


- **Severity:** Medium 4.0 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 7 Jun 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-82cp-844q-8p3h

## What is CVE-2022-30745?

CVE-2022-30745 is a medium-severity vulnerability in Samsung Mobile Quick Share, published on 7 Jun 2022. 

### Official description

Improper access control vulnerability in Quick Share prior to version 13.1.2.4 allows attacker to access internal files in Quick Share.

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Samsung Quick Share.

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

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

## Is CVE-2022-30745 being exploited?

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

## Other vulnerabilities in Samsung Mobile Quick Share

- [CVE-2023-42544](https://insights.sbomify.com/CVE-2023-42544/): Missing authorization in Quick Share (medium 5.5)
- [CVE-2022-39860](https://insights.sbomify.com/CVE-2022-39860/): Information disclosure in QuickShare (medium 4.4)
- [CVE-2024-49421](https://insights.sbomify.com/CVE-2024-49421/): Path traversal in Quick Share Agent (medium 4.3)
- [CVE-2023-21462](https://insights.sbomify.com/CVE-2023-21462/): Information disclosure in Quick Share Agent (medium 4.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-30745 is a medium-severity vulnerability in Samsung Mobile Quick Share, published on 7 Jun 2022. 
Exploitation: There is no known exploitation of CVE-2022-30745 in the wild and no public exploit code.

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

## Sources

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

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