CVE-2024-22752
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedInsecure 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceEaseUS MobiMover 6.0.5 Build 21620 contains insecure file permissions in its installation directory that allow local attackers to place or execute crafted executables, achieving privilege escalation to execute code with elevated system privileges.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify EaseUS MobiMover installation pathCheck common installation locations: C:\Program Files\EaseUS\MobiMover, C:\Program Files (x86)\EaseUS\MobiMover, or search for 'MobiMover' using dir /s C:\*MobiMover* in Command PromptAffected if EaseUS MobiMover is found installed on the system
-
Determine installed versionRight-click the MobiMover executable in the installation folder, select Properties, and check the Details tab for Version/Product Version. Alternatively, right-click the shortcut in Start Menu and check target path, then inspect the executable propertiesAffected if Version is 6.0.5 Build 21620 or the product version field shows MobiMover 6.0.5
-
Inspect folder permissions on installation directoryRight-click the installation folder (e.g., C:\Program Files\EaseUS\MobiMover), select Properties, go to Security tab, and examine the permissions for Users group and other standard user accountsAffected if Users group or standard non-admin users have Write or Write & Execute permissions to the folder
-
Verify executable placement capabilityAs a standard (non-admin) user, attempt to create a test file or copy an executable into the MobiMover installation folder using Command Prompt or File ExplorerAffected if Standard users can successfully write or copy files into the installation directory
-
Check for weak ACL configurationsRun icacls "C:\Program Files\EaseUS\MobiMover" (or actual path) in Command Prompt and review the output for (CI)(WI) or similar permissions granting write access to Users or EveryoneAffected if The Access Control List shows write or execute permissions granted to Users, Everyone, or authenticated users
If EaseUS MobiMover 6.0.5 Build 21620 is installed AND non-administrative users have write or execute permissions on its installation directory, the system is vulnerable to privilege escalation via this CVE.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRestrict write and execute permissions on the application installation directory to only authorized administrators and processes, removing any inherited or explicit permissions that allow standard users to modify or launch executables from that location.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-22752 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-22752 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data