dbcve.org
Endpoint SecurityApplication · Bitdefender

CVE-2024-2223

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
An Incorrect Regular Expression vulnerability in Bitdefender GravityZone Update Server allows an attacker to cause a Server Side Request Forgery and reconfigure the relay. 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 · moderate confidence

An incorrect regular expression in Bitdefender GravityZone Update Server allows attackers to perform Server Side Request Forgery (SSRF), enabling them to make the update server issue arbitrary network requests and reconfigure the relay. This pattern-matching flaw in the input validation leads to critical network-based code execution without authentication.

MitigationApply vendor-supplied patches for the affected versions (7.0.5.200089 for Linux, 7.9.9.380 for Windows, 6.36.1 for On-Premises Control Center) and restrict network access to the update server to limit SSRF exploitation vectors.

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. Check Bitdefender Endpoint Security for Linux version
    Run command: dpkg -l | grep bitdefender or rpm -qa | grep -i bitdefender to list installed Bitdefender packages and their versions
    Affected if Version equals 7.0.5.200089
  2. Check Bitdefender Endpoint Security for Windows version
    Open Control Panel > Programs and Features, or run: wmic product where "name like '%Bitdefender%'" get name,version
    Affected if Version equals 7.9.9.380
  3. Check GravityZone Control Center version
    Log into the on-premises Control Center web interface and navigate to Administration > System > About, or check the installed package version via: rpm -qa | grep -i gravityzone or dpkg -l | grep -i gravityzone
    Affected if Version equals 6.36.1
  4. Verify if Update Server component is enabled
    Check GravityZone update server configuration in Control Center under Network > Update Servers, or inspect configuration files in /opt/bitdefender/etc/gzuupdateserver.conf (Linux) or the Windows equivalent in ProgramData/Bitdefender/Enterprise_Security
    Affected if Update Server feature is enabled and accessible on the network

Your environment is affected if you have any of the exact versions (7.0.5.200089, 7.9.9.380, or 6.36.1) installed AND the GravityZone Update Server component is enabled and network-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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied patches for the affected versions (7.0.5.200089 for Linux, 7.9.9.380 for Windows, 6.36.1 for On-Premises Control Center) and restrict network access to the update server to limit SSRF exploitation vectors.

Fix this in Endpoint Security Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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