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

CVE-2024-13976

HIGH · 8.5 CVSS v4.0 Published 2025-07-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/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 DLL injection vulnerability exists in Commvault for Windows 11.20.0, 11.28.0, 11.32.0, 11.34.0, and 11.36.0. During the installation of maintenance updates, an attacker with local access may exploit uncontrolled search path or DLL loading behavior to execute arbitrary code with elevated privileges. The vulnerability has been resolved in versions 11.20.202, 11.28.124, 11.32.65, 11.34.37, and 11.36.15.

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 injection vulnerability in Commvault for Windows allows local attackers to execute arbitrary code with elevated privileges by exploiting uncontrolled search path or DLL loading behavior during maintenance update installation. This affects versions 11.20.0, 11.28.0, 11.32.0, 11.34.0, and 11.36.0.

MitigationUpgrade to patched versions 11.20.202, 11.28.124, 11.32.65, 11.34.37, or 11.36.15 as specified in the vendor advisory to resolve the DLL loading vulnerability.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/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 checks

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

  1. Confirm Commvault installation exists
    Look for Commvault installation directories (typically under Program Files/Commvault) or check for Commvault services in Windows Services (search for 'Commvault' entries)
    Affected if No Commvault installation found means not affected; if present, continue to version check
  2. Identify installed Commvault version
    Use Windows Programs and Features to view Commvault version, check the installation directory for version information, or run 'commvault -version' if a CLI tool exists
    Affected if Unable to determine version means further investigation needed; if version can be obtained, compare against fixed releases
  3. Compare version against fixed releases
    Compare your installed version to the following fixed versions: 11.20.202, 11.28.124, 11.32.65, 11.34.37, or 11.36.15. Versions below these thresholds are vulnerable.
    Affected if Installed version is below 11.20.202, 11.28.124, 11.32.65, 11.34.37, or 11.36.15 (or if version cannot be determined but Commvault is present)
  4. Assess maintenance update exposure
    Determine if the maintenance update functionality is accessible to local users. This vulnerability specifically affects the DLL loading behavior during maintenance update installation.
    Affected if Local users with access to trigger maintenance updates on a vulnerable version are at risk

You are affected if Commvault for Windows is installed with a version below 11.20.202, 11.28.124, 11.32.65, 11.34.37, or 11.36.15 and the maintenance update feature is accessible in your environment.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to patched versions 11.20.202, 11.28.124, 11.32.65, 11.34.37, or 11.36.15 as specified in the vendor advisory to resolve the DLL loading vulnerability.

Recommended fix High confidence

Upgrade to version 11.20.202, 11.28.124, 11.32.65, 11.34.37, or 11.36.15 (matching the major version line currently in use)

  1. Identify the currently installed Commvault version by checking the application or using the command line tools
  2. Download the corresponding fixed version from Commvault's official support portal: 11.20.202, 11.28.124, 11.32.65, 11.34.37, or 11.36.15
  3. Review the release notes and upgrade documentation for the target version before proceeding
  4. Schedule a maintenance window to perform the upgrade
  5. Create a full backup of the Commvault database and configuration
  6. Stop all Commvault services on the server before initiating the upgrade
  7. Run the installer for the fixed version with administrator privileges
  8. Follow the on-screen prompts to complete the installation of the maintenance update
Caveat Review Commvault release notes for any compatibility changes or deprecated features before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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