dbcve.org
Uncontrolled Search Path (DLL Hijack)Weakness · CWE-427

CVE-2025-1700

HIGH · 7.0 CVSS v3.1 Published 2025-07-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated
No privileges

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 · unedited
A DLL hijacking vulnerability was reported in the Motorola Software Fix (Rescue and Smart Assistant) installer that could allow a local attacker to escalate privileges during installation of the software.

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 confidence

This is a DLL hijacking vulnerability in the Motorola Software Fix (Rescue and Smart Assistant) installer. During installation, the application loads DLLs from locations where a local attacker could place a malicious DLL, allowing privilege escalation to occur when the installer runs with elevated privileges.

MitigationApply the vendor patch when available. In the interim, ensure the installation directory is protected against write access by non-privileged users and run installations in controlled, secure environments.

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
Local
Complexity
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/PR:N/UI:R/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Motorola Software Fix installer is present
    Search for executables named 'Rescue' or 'Smart Assistant' or related installer files in common installation directories (C:\Program Files\Motorola, C:\Program Files (x86)\Motorola) or check the system for installed Motorola software via registry or installed programs list
    Affected if The Motorola Software Fix (Rescue and Smart Assistant) installer or application is found on the system
  2. Locate the installation directory
    Find the directory where the Motorola software is installed. If the product is actively installed, identify the main executable location
    Affected if The software is installed in a directory writable by non-privileged users
  3. Check directory permissions on the installation folder
    Use icacls or file explorer security properties to examine write permissions on the Motorola installation directory - verify which users/groups have Write or Create Files permissions
    Affected if Non-privileged users (especially Everyone, Users, or authenticated users) have Write permissions to directories from which the installer loads DLLs
  4. Inspect DLL search path locations
    Examine the directories the installer may load DLLs from: the application directory, system directories, and PATH. Use Process Monitor or similar tool during a test installation to observe DLL loading behavior
    Affected if DLLs can be loaded from directories writable by low-privilege attackers (user's temp folders, world-writable directories, or the application directory itself)
  5. Check for pre-existing suspicious DLLs
    List all DLL files in the installation directory and any directories in the DLL search path. Look for unexpected or recently placed DLLs with names that may be commonly hijacked (e.g., version.dll, winhttp.dll, dbghelp.dll)
    Affected if Unexpected DLL files exist in locations where the installer loads from, indicating potential compromise

A user is affected if the Motorola Software Fix (Rescue and Smart Assistant) installer is present and the installation directory or DLL search path locations are writable by non-privileged users, allowing DLL hijacking for privilege escalation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor patch when available. In the interim, ensure the installation directory is protected against write access by non-privileged users and run installations in controlled, secure environments.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-1700 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-1700 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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