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

CVE-2024-7324

HIGH · 7.8 CVSS v3.1 Published 2024-07-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

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 vulnerability was found in IObit iTop Data Recovery Pro 4.4.0.687. It has been declared as critical. Affected by this vulnerability is an unknown functionality in the library madbasic_.bpl of the component BPL Handler. The manipulation leads to uncontrolled search path. Local access is required to approach this attack. The associated identifier of this vulnerability is VDB-273247. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.

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 confidence

A DLL hijacking vulnerability exists in IObit iTop Data Recovery Pro 4.4.0.687 where the BPL handler (madbasic_.bpl) loads libraries from an uncontrolled search path. An attacker with local access could place malicious DLLs in a directory searched by the application to achieve arbitrary code execution.

MitigationSince the vendor has not responded to disclosure, implement application isolation (run under a restricted user account) and ensure the application directory is protected from write access by untrusted users. Consider alternative software until a vendor patch becomes available.

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
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 checks

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

  1. Identify installed version of IObit iTop Data Recovery
    Open the application, go to Help > About, or right-click the executable in the application directory and view Properties > Details to find the version number
    Affected if The installed version is exactly 4.4.0.687
  2. Locate the vulnerable BPL handler file
    Browse to the application installation directory (typically C:\Program Files\IObit\iTop Data Recovery or C:\Program Files (x86)\IObit\iTop Data Recovery) and search for the file madbasic_.bpl
    Affected if The file madbasic_.bpl exists in the application directory
  3. Verify the application directory is writable by untrusted users
    Right-click the application installation folder, select Properties > Security, and check the permissions for Users or other non-admin groups. Alternatively, run icacls <directory> from an unprivileged command prompt to list effective permissions
    Affected if Users or Authenticated Users have Write or Modify permissions on the application directory
  4. Check for presence of common DLLs in application directory that could be hijacked
    List all DLL files in the application directory. Look for commonly hijacked DLLs such as msvcr120.dll, msvcp120.dll, or other runtime libraries that the application might attempt to load from the current directory
    Affected if Any non-Microsoft or third-party DLLs are present in the application directory that could be replaced by a malicious version
  5. Confirm the BPL handler is loaded during normal operation
    Run Process Monitor (from Sysinternals) with a filter for the iTop Data Recovery executable. Look for LoadLibrary events referencing the madbasic_.bpl module or DLLs being loaded from the application directory
    Affected if The application loads modules from the same directory as madbasic_.bpl during startup or normal use

You are affected if the installed version is exactly 4.4.0.687, the madbasic_.bpl file exists, and the application directory or a directory in the DLL search path is writable by untrusted users.

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

Since the vendor has not responded to disclosure, implement application isolation (run under a restricted user account) and ensure the application directory is protected from write access by untrusted users. Consider alternative software until a vendor patch becomes available.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
3.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-7324 — 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-2024-7324 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