# CVE-2022-22285: Code injection in Reminder

> Attackers can hijack PendingIntents in the Samsung Reminder app to execute privileged actions, requiring a patch to prevent code injection.

- **Severity:** Medium 4.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 7 Jan 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-4m5x-p265-j28q

## What is CVE-2022-22285?

CVE-2022-22285 is a medium-severity code injection vulnerability in Samsung Mobile Reminder, published on 7 Jan 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

A vulnerability using PendingIntent in Reminder prior to version 12.2.05.0 in Android R(11.0) and 12.3.02.1000 in Android S(12.0) allows attackers to execute privileged action by hijacking and modifying the intent.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Samsung Reminder.

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

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

## Is CVE-2022-22285 being exploited?

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

## Other vulnerabilities in Samsung Mobile Reminder

- [CVE-2022-39876](https://insights.sbomify.com/CVE-2022-39876/): Information disclosure in Reminder (medium 5.9)
- [CVE-2022-23433](https://insights.sbomify.com/CVE-2022-23433/): Missing authorization in Reminder (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-22285 is a medium-severity code injection vulnerability in Samsung Mobile Reminder, published on 7 Jan 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-22285 in the wild and no public exploit code.

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

## Sources

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

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