dbcve.org
Endpoint SecurityApplication · Bitdefender

CVE-2024-2224

CRITICAL · 9.8 CVSS v3.1 Published 2024-04-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 the following products that include the vulnerable component: Bitdefender Endpoint Security for Linux version 7.0.5.200089 Bitdefender Endpoint Security for Windows version 7.9.9.380 GravityZone Control Center (On Premises) version 6.36.1

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 exists in the UpdateServer component of Bitdefender GravityZone products. The vulnerability allows attackers to escape restricted directories and access or write files outside the intended path, leading to arbitrary code execution on vulnerable instances.

MitigationApply vendor-supplied patches or update to non-vulnerable versions of the affected Bitdefender products (7.0.5.200089 for Linux, 7.9.9.380 for Windows, and 6.36.1 for GravityZone Control Center).

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
Endpoint SecurityApplication
Affected:= 7.0.5.200089= 7.9.9.380
Gravityzone Control CenterApplication
Affected:= 6.36.1

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

CVSS:3.1/AV:N/AC:L/PR:N/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 Bitdefender Endpoint Security installation
    On Windows, check 'Add or Remove Programs' or run 'wmic product get name,version'. On Linux, check for installed packages via package manager (dpkg -l, rpm -qa) looking for 'Bitdefender Endpoint Security' or 'GravityZone' packages.
    Affected if Bitdefender Endpoint Security is installed and version is 7.0.5.200089 (Linux) or 7.9.9.380 (Windows)
  2. Identify GravityZone Control Center installation
    Check for installed packages on the server looking for 'GravityZone' or 'Bitdefender GravityZone Control Center' components. On Linux, use package manager queries.
    Affected if GravityZone Control Center is installed and version is 6.36.1
  3. Confirm UpdateServer component presence
    Check if the UpdateServer component is installed and running. Look for update server services or binaries (common names include 'updateServer', 'updateserver', or similar in Bitdefender installation directories).
    Affected if UpdateServer component is present and running on the affected product version
  4. Compare installed version against affected versions
    Retrieve the exact installed version number using vendor tools, registry, or installation directories. Compare against the affected versions: 7.0.5.200089, 7.9.9.380 for Endpoint Security; 6.36.1 for Control Center.
    Affected if Installed version matches or falls within the affected version range

The system is affected if Bitdefender Endpoint Security (versions 7.0.5.200089 or 7.9.9.380) or GravityZone Control Center (version 6.36.1) is installed with the UpdateServer component enabled.

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-supplied patches or update to non-vulnerable versions of the affected Bitdefender products (7.0.5.200089 for Linux, 7.9.9.380 for Windows, and 6.36.1 for GravityZone Control Center).

Fix this in Endpoint Security Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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