CVE-2024-7612
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 in Ivanti EPMM before 12.1.0.4 allow a local authenticated attacker to modify sensitive application components.
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 · moderate confidenceIvanti EPMM (Endpoint Manager Mobile) versions prior to 12.1.0.4 contain insecure file system or application permissions that allow any locally authenticated user to modify sensitive application components, potentially leading to privilege escalation or system compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 12.0.0.5>= 12.1.0.0, < 12.1.0.4CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 installed Ivanti EPMM versionAccess the EPMM admin console and navigate to System Settings > About, or check the version via the API endpoint /mifs/about or by inspecting the installed package on the server filesystem.Affected if The installed version is below 12.0.0.5, or falls between 12.1.0.0 and 12.1.0.3 inclusive.
-
Verify file system permissions on application directoriesOn the EPMM server, use file system auditing tools (such as icacls on Windows or ls -la on Linux) to examine write permissions on the application installation directory (commonly found under /opt/ or C:\Program Files\Ivanti\) and subdirectories containing executable binaries and configuration files.Affected if Any locally authenticated user account (non-admin) has write or modify permissions to sensitive application directories, binaries, or configuration files.
-
Check service account permissionsReview the permissions of the service account running the EPMM application. Examine whether low-privilege users can modify service executable paths or related binaries.Affected if The service account has excessive permissions allowing modification by standard user accounts, or service binaries are writable by non-admin users.
-
Audit configuration file permissionsInspect permission settings on configuration files within the EPMM installation, particularly those storing credentials, encryption keys, or sensitive system parameters.Affected if Configuration files are readable or writable by non-administrative local users.
A user is affected if the installed Ivanti EPMM version is below 12.1.0.4 (or below 12.0.0.5) AND standard authenticated users have excessive file system permissions on application components.
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.
dbcve · scoped12.0.0.512.1.0.4
Upgrade Ivanti EPMM to version 12.1.0.4 or later to obtain the vendor patch that corrects the permission model.
Upgrade to Ivanti EPMM 12.0.0.5 or 12.1.0.4 (or later) depending on current branch
- 1. Identify the currently installed Ivanti Endpoint Manager Mobile (EPMM) version
- 2. If running version 12.0.x and below (less than 12.0.0.5), plan upgrade to version 12.0.0.5
- 3. If running version 12.1.0.0 through 12.1.0.3, plan upgrade to version 12.1.0.4 or later
- 4. Review Ivanti upgrade documentation and release notes for upgrade prerequisites
- 5. Perform a backup of the current EPMM configuration
- 6. Execute the upgrade to the appropriate fixed version
- 7. Verify the upgrade was successful and the application is functioning correctly
- 8. Confirm the insecure permissions vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-7612 — 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-7612 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