# CVE-2021-25442: Auth bypass in Knox Mobile Enrollment

> Attackers can bypass Knox Manage authentication via improper MDM policy management in Samsung Knox Mobile Enrollment.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jul 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-j523-5388-rcgr

## What is CVE-2021-25442?

CVE-2021-25442 is a high-severity authentication bypass vulnerability in Samsung Mobile Knox Mobile Enrollment, published on 8 Jul 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper MDM policy management vulnerability in KME module prior to KCS version 1.39 allows MDM users to bypass Knox Manage authentication.

Weakness: CWE-287 (Improper Authentication), CWE-269 (Improper Privilege Management)

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

It affects 1 product.


Products: Samsung Knox Cloud Services.

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

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

## Is CVE-2021-25442 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-25442 is a high-severity authentication bypass vulnerability in Samsung Mobile Knox Mobile Enrollment, published on 8 Jul 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-25442 in the wild and no public exploit code.

Affected product: Samsung Mobile Knox Mobile Enrollment. 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-25442/ (Markdown: https://insights.sbomify.com/CVE-2021-25442/index.md)
```

## Sources

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

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