# CVE-2022-36835: Information disclosure in Samsung Internet Browser

> Attackers can access arbitrary files via implicit intent hijacking in Samsung Internet Browser, exposing sensitive user data.

- **Severity:** Low 3.3 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 5 Aug 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-2x5h-982r-4f38

## What is CVE-2022-36835?

CVE-2022-36835 is a low-severity vulnerability in Samsung Internet Browser, published on 5 Aug 2022. 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

Implicit Intent hijacking vulnerability in Samsung Internet Browser prior to version 17.0.7.34 allows attackers to access arbitrary files.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Samsung Samsung Internet Browser.

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

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

## Is CVE-2022-36835 being exploited?

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

## Other vulnerabilities in Samsung Internet Browser

- [CVE-2018-10496](https://insights.sbomify.com/CVE-2018-10496/): Use after free in Samsung Internet Browser (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-36835 is a low-severity vulnerability in Samsung Internet Browser, published on 5 Aug 2022. 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-2022-36835 in the wild and no public exploit code.

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

## Sources

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

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