# CVE-2021-25441: Path traversal in AR Emoji Editor

> Untrusted applications can access arbitrary files with escalated privileges due to improper input validation in the AR Emoji Editor.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jul 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-xj87-rp3c-q5f4

## What is CVE-2021-25441?

CVE-2021-25441 is a high-severity path traversal vulnerability in Samsung Mobile AR Emoji Editor, published on 8 Jul 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper input validation vulnerability in AR Emoji Editor prior to version 4.4.03.5 in Android Q(10.0) and above allows untrusted applications to access arbitrary files with an escalated privilege.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2021-25441?

It affects 1 product.


Products: Samsung Ar Emoji Editor.

## How do I fix CVE-2021-25441?

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

## Is CVE-2021-25441 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-25441 and fix it if it is affected.

What it is: CVE-2021-25441 is a high-severity path traversal vulnerability in Samsung Mobile AR Emoji Editor, published on 8 Jul 2021. 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-2021-25441 in the wild and no public exploit code.

Affected product: Samsung Mobile AR Emoji Editor. 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-2021-25441/ (Markdown: https://insights.sbomify.com/CVE-2021-25441/index.md)
```

## Sources

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

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