# CVE-2022-36837: Information disclosure in Samsung email

> An attacker can exploit an intent redirection flaw in the Samsung email app to access sensitive user information.

- **Severity:** Medium 6.2 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:** 5 Aug 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-mmw8-77j5-hmqm

## What is CVE-2022-36837?

CVE-2022-36837 is a medium-severity vulnerability in Samsung email, published on 5 Aug 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Intent redirection vulnerability using implicit intent in Samsung email prior to version 6.1.70.20 allows attacker to get sensitive information.

Weakness: CWE-285 (Improper Authorization)

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

It affects 1 product.


Products: Samsung Samsung Email.

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

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

## Is CVE-2022-36837 being exploited?

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

## Other vulnerabilities in Samsung email

- [CVE-2018-10497](https://insights.sbomify.com/CVE-2018-10497/): Code injection in Samsung Email (high 7.8)
- [CVE-2018-10498](https://insights.sbomify.com/CVE-2018-10498/): Path traversal in Samsung Email (medium 5.5)
- [CVE-2022-36864](https://insights.sbomify.com/CVE-2022-36864/): Missing authorization in Samsung Email (medium 4.0)
- [CVE-2022-22287](https://insights.sbomify.com/CVE-2022-22287/): Path traversal in Samsung Email (low 3.9)

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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