dbcve.org
GravityzoneApplication · Bitdefender

CVE-2021-3960

HIGH · 7.8 CVSS v3.1 Published 2021-12-16
Fix available
A fix is available. Upgrade to 3.3.8.272 or later.
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
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the UpdateServer component of Bitdefender GravityZone allows an attacker to execute arbitrary code on vulnerable instances. This issue affects Bitdefender GravityZone versions prior to 3.3.8.272

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 path traversal vulnerability in the UpdateServer component of Bitdefender GravityZone allows attackers to escape restricted directories and execute arbitrary code on affected instances. The vulnerability stems from improper input validation on pathname parameters within the update mechanism.

MitigationUpgrade Bitdefender GravityZone to version 3.3.8.272 or later to remediate this vulnerability. Organizations should prioritize patching this high-severity flaw given its potential for remote code execution.

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
GravityzoneApplication
Affected:< 3.3.8.272

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. Confirm Bitdefender GravityZone installation
    Locate GravityZone installation directories or check system services for GravityZone components (typically installed in /opt/bitdefender or similar system paths)
    Affected if Bitdefender GravityZone is not found on the system, this CVE does not apply
  2. Identify installed GravityZone version
    Check the installed version of Bitdefender GravityZone using product-specific commands, configuration files, or the management console. Compare against version 3.3.8.272
    Affected if Installed version is lower than 3.3.8.272 (e.g., 3.3.8.200, 3.3.7.150, etc.)
  3. Verify UpdateServer component status
    Check if the UpdateServer component is running or enabled within the GravityZone installation. This may be visible in the management console or through process/service enumeration
    Affected if UpdateServer component is active and the version is below 3.3.8.272
  4. Inspect update mechanism configuration
    Review the update mechanism configuration files or settings within GravityZone to confirm pathname parameters can be externally controlled or manipulated
    Affected if Update mechanism accepts user-supplied path parameters and version is vulnerable

A system is affected if Bitdefender GravityZone is installed with a version lower than 3.3.8.272 and the UpdateServer component is enabled and accessible.

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
Upgrade available Upgrade to 3.3.8.272 or later
Fixed in 3.3.8.272
Interim mitigation

Upgrade Bitdefender GravityZone to version 3.3.8.272 or later to remediate this vulnerability. Organizations should prioritize patching this high-severity flaw given its potential for remote code execution.

Recommended fix High confidence

GravityZone 3.3.8.272 or later

  1. 1. Backup all GravityZone configuration data and databases according to Bitdefender backup procedures
  2. 2. Verify current GravityZone version is below 3.3.8.272 via the administration console or command line
  3. 3. Download GravityZone version 3.3.8.272 or later from the official Bitdefender download portal or support channel
  4. 4. Review Bitdefender's official upgrade documentation for GravityZone before proceeding
  5. 5. Apply the upgrade following Bitdefender's standard upgrade procedure (typically via the administration console or dedicated installer)
  6. 6. After upgrade completes, verify the new version is 3.3.8.272 or later
  7. 7. Confirm the UpdateServer component is functioning correctly and the path traversal vulnerability is resolved

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

Fix this in Gravityzone Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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