# CVE-2022-36851: Improper access control vulnerability in Samsung pass prior to version 4.0.03.1 allow physical attackers to access data of Samsung pass on a


- **Severity:** Low 3.9 (`CVSS:3.1/AV:P/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 9 Sep 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-p8qw-j9ch-6x9w

## What is CVE-2022-36851?

CVE-2022-36851 is a low-severity vulnerability in Samsung pass, published on 9 Sep 2022. 

### Official description

Improper access control vulnerability in Samsung pass prior to version 4.0.03.1 allow physical attackers to access data of Samsung pass on a certain state of an unlocked device.

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Samsung Samsung Pass.

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

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

## Is CVE-2022-36851 being exploited?

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

## Other vulnerabilities in Samsung pass

- [CVE-2022-30730](https://insights.sbomify.com/CVE-2022-30730/): Missing authorization in Samsung Pass (medium 4.6)
- [CVE-2022-27841](https://insights.sbomify.com/CVE-2022-27841/): Auth bypass in Samsung Pass (medium 4.3)
- [CVE-2021-25505](https://insights.sbomify.com/CVE-2021-25505/): Auth bypass in Samsung Pass (low 3.3)
- [CVE-2022-36876](https://insights.sbomify.com/CVE-2022-36876/): Missing authorization in Samsung Pass (low 1.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-36851 is a low-severity vulnerability in Samsung pass, published on 9 Sep 2022. 
Exploitation: There is no known exploitation of CVE-2022-36851 in the wild and no public exploit code.

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

## Sources

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

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