# CVE-2024-22752: Privilege escalation in n/a

> Attackers can gain escalated privileges by launching a crafted executable from the EaseUS MobiMover installation directory due to insecure permissions.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Mar 2024
- **Updated:** 29 Aug 2024
- **Also known as:** GHSA-mr9m-vh5h-8j6x

## What is CVE-2024-22752?

CVE-2024-22752 is a high-severity vulnerability in n/a, published on 7 Mar 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Insecure permissions issue in EaseUS MobiMover 6.0.5 Build 21620 allows attackers to gain escalated privileges via use of crafted executable launched from the application installation directory.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2024-22752?


## How do I fix CVE-2024-22752?

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

## Is CVE-2024-22752 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-22752 exists.

Public exploit code:

- EaseUS MobiMover 6.0.5 Build 21620 - Insecure Files and Folders Permissions (github_poc): https://github.com/hacker625/CVE-2024-22752

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-22752 and fix it if it is affected.

What it is: CVE-2024-22752 is a high-severity vulnerability in n/a, published on 7 Mar 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-22752 exists.

Affected product: n/a. 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-2024-22752/ (Markdown: https://insights.sbomify.com/CVE-2024-22752/index.md)
```

## Sources

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

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