CVE-2025-1701
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 · uneditedCVE-2025-1701 is a high-severity vulnerability in the MIM Admin service. An attacker could exploit this vulnerability by sending a specially crafted request over the RMI interface to execute arbitrary code with the privileges of the MIM Admin service. The RMI interface is only accessible locally (listening on 127.0.0.1), limiting the attack vector to the local machine. This means that in a properly configured hospital environment, an attacker must have already compromised the network and additionally compromised the system where the MIM Admin service is running. From there, attackers with sufficient knowledge of MIM's implementation, library usage, and functionality with access to extend the MIM RMI library could force the MIM Admin service to run commands on the local machine with its privileges. Users of MIM Software products exposed via RDP or multi-user application virtualization system should take note that the system being exposed is the environment hosting the virtualized MIM client. This issue affects MIM Admin Service: before 7.2.13, 7.3.8, 7.4.3
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 confidenceMIM Admin service contains a high-severity vulnerability in its RMI interface (listening on 127.0.0.1) that allows authenticated local attackers to execute arbitrary code with MIM Admin service privileges. Exploitation requires the attacker to have already compromised the system and possess specific knowledge of MIM's implementation and library usage.
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
- Adjacent
- Complexity
- Low
- Privileges
- Low
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:A/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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 MIM Admin Service installationSearch for Microsoft Identity Manager (MIM) components on the system. Check for directories named 'MIM', 'Microsoft Identity Manager', or the MIM service in Windows Services (look for 'MIM Admin service' or 'FIMAdmin' service).Affected if MIM Admin Service is installed on the system
-
Determine MIM Admin Service versionLocate the MIM installation directory and check the version information of the MIM Admin service executable or DLL. Common paths include C:\Program Files\Microsoft Identity Manager\ or check the service executable properties.Affected if The installed version is 7.2.x before 7.2.13, 7.3.x before 7.3.8, or 7.4.x before 7.4.3 (versions earlier than the fixed releases)
-
Verify RMI interface is bound to localhostRun 'netstat -an | findstr 127.0.0.1' or use PowerShell to check for listening ports associated with MIM. The RMI interface should only bind to 127.0.0.1 as stated in the CVE description.Affected if The RMI interface is listening on interfaces other than 127.0.0.1, exposing the service to network attackers
-
Check service account privilegesOpen Services, find the MIM Admin service, right-click and select Properties, then check the 'Log On' tab. Note the account under which the service runs.Affected if The MIM Admin service runs with elevated privileges and could allow privilege escalation if exploited
-
Review access controls on the systemCheck if the system has proper access controls, particularly for RDP or multi-user application virtualization. Review local user accounts and group memberships that could provide authenticated access.Affected if Multiple untrusted users have authenticated access to the system, increasing the risk that a local attacker could exploit this vulnerability
A system is affected if MIM Admin Service is installed with a version prior to 7.2.13, 7.3.8, or 7.4.3 AND the system has untrusted authenticated users who could leverage the localhost-bound RMI interface.
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 · scopedUpgrade MIM Admin Service to version 7.2.13, 7.3.8, or 7.4.3 or later. Additionally, ensure systems are not exposed via RDP or multi-user application virtualization without proper access controls, as this could expand the attack surface.
Upgrade to MIM Admin Service 7.2.13, 7.3.8, or 7.4.3 (whichever corresponds to the current release branch in use)
- Identify the currently installed MIM Admin Service version by checking the installed software or service properties
- Determine which release branch (7.2.x, 7.3.x, or 7.4.x) is currently in use
- Obtain the appropriate upgrade package from MIM Software (www.mimsoftware.com) - select the corresponding fixed version (7.2.13, 7.3.8, or 7.4.3) for the branch in use
- Backup the existing MIM Admin Service configuration and any related data per hospital/institution backup procedures
- Stop the MIM Admin Service before applying the upgrade
- Install the upgraded MIM Admin Service version
- Verify the service starts successfully and the version is correctly reported
- Test that MIM functionality remains operational after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-1701 — 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-2025-1701 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