dbcve.org
CommcellApplication · Commvault

CVE-2021-34997

HIGH · 8.8 CVSS v3.1 Published 2022-01-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
This vulnerability allows remote attackers to execute arbitrary code on affected installations of Commvault CommCell 11.22.22. Although authentication is required to exploit this vulnerability, the existing authentication mechanism can be bypassed. The specific flaw exists within the AppStudioUploadHandler class. The issue results from the lack of proper validation of user-supplied data, which can allow the upload of arbitrary files. An attacker can leverage this vulnerability to execute code in the context of NETWORK SERVICE. Was ZDI-CAN-13894.

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

This is a file upload vulnerability in Commvault CommCell's AppStudioUploadHandler class where improper validation of user-supplied data allows authenticated attackers to upload arbitrary files. Although authentication is required, the authentication mechanism itself can be bypassed, enabling remote attackers to execute code in the context of NETWORK SERVICE.

MitigationApply vendor patch for CVE-2021-34997. As compensating controls, restrict network access to CommCell management interfaces, implement strict file type validation on upload endpoints, and ensure authentication mechanisms cannot be bypassed.

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
CommcellApplication
Affected:= 11.22.22

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

CVSS:3.1/AV:N/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 if Commvault CommCell is installed
    Look for Commvault installation directories or check for Commvault services running on the system. Common locations include C:\Program Files\Commvault\ or /opt/commvault/ on Linux systems.
    Affected if Commvault CommCell software is present on the system
  2. Check the Commvault CommCell version
    Use the Commvault command line interface (qoperation execscript -sn GetVersion) or check the About section in the CommCell Console. Alternatively, check registry keys or version files in the installation directory.
    Affected if The installed version is exactly 11.22.22
  3. Verify if AppStudio web interface is accessible
    Check if the CommCell web console or AppStudio interface is exposed on the network. Look for endpoints related to upload functionality, typically found under /webconsole/ or /api/ paths.
    Affected if The AppStudio upload handler endpoint is reachable from the network
  4. Check authentication configuration
    Review Commvault authentication settings in the CommCell Console under Security > Authentication. Look for any misconfigured or weak authentication settings that could allow bypass.
    Affected if Authentication can be bypassed or is improperly configured
  5. Identify if arbitrary file upload is possible
    Test the AppStudioUploadHandler endpoint with a harmless file upload request if you have authorized access to the CommCell. Inspect any web logs for evidence of unauthorized file uploads.
    Affected if The upload handler accepts files without proper validation

A system is affected if it runs Commvault CommCell version 11.22.22 with the AppStudio upload handler exposed and accessible, especially if authentication bypass is possible.

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 vendor patch for CVE-2021-34997. As compensating controls, restrict network access to CommCell management interfaces, implement strict file type validation on upload endpoints, and ensure authentication mechanisms cannot be bypassed.

Fix this in Commcell 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-2021-34997 — 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-2021-34997 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