dbcve.org
GravityzoneApplication · Bitdefender

CVE-2017-8931

CRITICAL · 9.8 CVSS v3.0 Published 2018-10-30
Fix available
A fix is available. Upgrade to 6.2.1-35 or later.
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
Bitdefender GravityZone VMware appliance before 6.2.1-35 might allow attackers to gain access with root privileges via unspecified vectors.

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

Critical pre-authentication vulnerability in Bitdefender GravityZone VMware appliance allowing attackers to gain root privileges. The specific attack vector and vulnerability type are not disclosed in available documentation. Affects versions prior to 6.2.1-35.

MitigationUpgrade to Bitdefender GravityZone VMware appliance version 6.2.1-35 or later. Given the critical severity and root-level access, also restrict network access to the management interface and implement network segmentation until the patch is applied.

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:< 6.2.1-35

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.0/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. Confirm Bitdefender GravityZone VMware appliance is running
    Access the VMware vSphere client or use 'vim-cmd vmsvc/getallvms' to list all VMs. Look for a VM named 'GravityZone' or similar Bitdefender appliance. Check the guest OS or VM notes for product identification.
    Affected if The system is a Bitdefender GravityZone VMware appliance (any version)
  2. Retrieve the GravityZone appliance version via web interface
    Log into the GravityZone admin web interface (typically https://<appliance-ip>:8443). Navigate to System > Updates or System > About. Locate the version number displayed.
    Affected if Unable to retrieve version from web interface or interface is unreachable
  3. Retrieve the GravityZone appliance version via command line
    Access the appliance via SSH or console. Run command: 'cat /opt/bitdefender/etc/GravityZone/VERSION' or 'cat /etc/product.version' (paths may vary). Check for a file containing version information.
    Affected if Command returns no version file or access is denied
  4. Compare installed version against affected range
    Take the retrieved version number (e.g., 6.2.1-20, 6.1.5-10) and compare numerically to 6.2.1-35. Versions below 6.2.1-35 are affected. Note: The dash number after 6.2.1 is the build/patch version.
    Affected if The version is lower than 6.2.1-35 (for example, 6.2.1-20 or 6.1.x)
  5. Check if management interface is exposed to untrusted networks
    Review firewall rules and network configuration. Determine if the GravityZone management ports (default 8443 for HTTPS, 443) are accessible from networks outside the trusted administrative zone.
    Affected if Management interface is accessible from untrusted networks (internet, guest VLANs, or untrusted internal subnets)

A user is affected if they are running a Bitdefender GravityZone VMware appliance with version lower than 6.2.1-35 and the management interface is 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.

dbcve · scoped
Upgrade available Upgrade to 6.2.1-35 or later
Fixed in 6.2.1-35
Interim mitigation

Upgrade to Bitdefender GravityZone VMware appliance version 6.2.1-35 or later. Given the critical severity and root-level access, also restrict network access to the management interface and implement network segmentation until the patch is applied.

Recommended fix Moderate confidence

6.2.1-35 or later

  1. Obtain the Bitdefender GravityZone VMware appliance version 6.2.1-35 or later from the official Bitdefender website (www.bitdefender.com)
  2. Create a complete backup of the current appliance configuration and data
  3. Deploy the updated VMware appliance using version 6.2.1-35 or later
  4. Restore the configuration from the backup to the new appliance
  5. Verify the upgrade was successful by checking the appliance version in the administration console

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

Fix this in Gravityzone Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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