dbcve.org
Driver BoosterApplication · Iobit

CVE-2024-7325

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 Driver Booster 11.0.0.0. It has been rated as critical. Affected by this issue is some unknown functionality in the library VCL120.BPL of the component BPL Handler. The manipulation leads to uncontrolled search path. Attacking locally is a requirement. The identifier of this vulnerability is VDB-273248. 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/BPL search order hijacking vulnerability in the VCL120.BPL library within the BPL Handler component of IObit Driver Booster 11.0.0.0 allows local attackers to execute arbitrary code by placing a malicious DLL in the search path before the application loads its intended library.

MitigationImplement secure DLL loading by using full absolute paths for all library loads, enabling Safe DLL Search Mode (SetDllDirectory), and ensuring the application loads only from trusted locations; consider code review of all LoadLibrary calls in the BPL Handler.

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
Driver BoosterApplication
Affected:= 11.0.0.0

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. Verify IObit Driver Booster version
    Open Programs and Features (appwiz.cpl) or check the application's About/Help section to find the installed version number of IObit Driver Booster
    Affected if The installed version is exactly 11.0.0.0
  2. Locate VCL120.BPL library file
    Search the IObit Driver Booster installation directory (typically C:\Program Files\IObit\Driver Booster or C:\Program Files (x86)\IObit\Driver Booster) for the presence of VCL120.BPL
    Affected if The file VCL120.BPL exists in the application directory
  3. Identify DLL search path directories
    Open a command prompt, navigate to the IObit Driver Booster installation folder, and run 'where VCL120.BPL' or examine the folder permissions. Check directories in the system PATH that appear before the application directory
    Affected if The application loads VCL120.BPL without using a full absolute path, or writable directories exist in the DLL search path before the application directory
  4. Check for user-writable locations in DLL search order
    Review folders such as the application directory, current working directory, and system directories (System32, SysWOW64) for write permissions. Use 'icacls' command on each directory to check write access
    Affected if Any directory in the DLL search order (especially the application directory or PATH directories) is writable by standard users, allowing placement of a malicious DLL
  5. Confirm BPL Handler component is in use
    Run IObit Driver Booster and monitor loaded modules using Process Explorer or Process Monitor (procmon.exe) to verify VCL120.BPL is being loaded at runtime
    Affected if The application loads VCL120.BPL dynamically during normal operation without specifying a full path

You are affected if IObit Driver Booster version 11.0.0.0 is installed and VCL120.BPL is present, especially if any directory in the DLL search path is writable by non-admin 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

Implement secure DLL loading by using full absolute paths for all library loads, enabling Safe DLL Search Mode (SetDllDirectory), and ensuring the application loads only from trusted locations; consider code review of all LoadLibrary calls in the BPL Handler.

Fix this in Driver Booster Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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