dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2024-13975

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 local privilege escalation vulnerability exists in Commvault for Windows versions 11.20.0, 11.28.0, 11.32.0, 11.34.0, and 11.36.0. In affected configurations, a local attacker who owns a client system with the file server agent installed can compromise any assigned Windows access nodes. This may allow unauthorized access or lateral movement within the backup infrastructure. The issue has been resolved in versions 11.32.60, 11.34.34, and 11.36.8.

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 local privilege escalation vulnerability in Commvault for Windows allows an attacker with ownership of a client system running the file server agent to compromise assigned Windows access nodes, potentially enabling unauthorized access or lateral movement within the backup infrastructure.

MitigationUpgrade Commvault installations to version 11.32.60, 11.34.34, or 11.36.8 or later to resolve the 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. Verify Commvault is installed on the system
    Check for Commvault installation directory at C:\Program Files\Commvault\ContentStore\ or look for Commvault services in Services.msc
    Affected if Commvault software is not found on the system, the system is not affected by this CVE
  2. Identify the installed Commvault version
    Run 'commvault -version' from the Command Prompt in the Commvault bin directory, or check the registry key HKLM\SOFTWARE\Commvault Systems\Galaxy\Instance001\CVLTVersion
    Affected if The installed version is lower than 11.32.60, 11.34.34, or 11.36.8 (any version prior to these patch releases)
  3. Confirm the file server agent is deployed
    Open Commvault Command Center or run 'qlist -ia' to list installed agents; look for 'File Server' agent type
    Affected if A file server agent is assigned to and running on this client system
  4. Check for assigned Windows access nodes
    In Commvault Command Center, navigate to the file server agent settings to view assigned access nodes, or run 'qoperation exec -app 'File Server' -cmd 'GetAgent'' to query access node assignments
    Affected if This client has one or more Windows access nodes assigned to it for backup operations
  5. Verify service account context of Commvault services
    Open Services.msc, locate Commvault services (like 'Commvault Galaxy Service'), right-click and check the 'Log On' account configuration
    Affected if The Commvault services run under a privileged domain account rather than a restricted service account

The system is affected if Commvault for Windows is installed with a version below 11.32.60, 11.34.34, or 11.36.8 AND the file server agent is running with access nodes assigned, allowing an attacker with client ownership to escalate privileges to those access nodes.

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 Commvault installations to version 11.32.60, 11.34.34, or 11.36.8 or later to resolve the vulnerability.

Recommended fix High confidence

Upgrade to Commvault 11.32.60, 11.34.34, or 11.36.8 depending on your current release branch

  1. Identify your current Commvault version by checking the About section in the Commvault Command Center or via the CVLTVersion registry key
  2. Determine which upgrade path applies: if on 11.32.x, upgrade to 11.32.60; if on 11.34.x, upgrade to 11.34.34; if on 11.36.x, upgrade to 11.36.8
  3. Download the applicable service pack from the Commvault Support Portal or your designated update repository
  4. Stop all Commvault services on the affected server before upgrading
  5. Execute the Commvault installer and follow the on-screen prompts to apply the upgrade
  6. Restart Commvault services after the upgrade completes
  7. Verify the installed version matches the expected fixed version via the Command Center or CVLTVersion
  8. Test that the file server agent and access node functionality operate normally

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

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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