dbcve.org
GravityzoneApplication · Bitdefender

CVE-2024-6980

CRITICAL · 9.8 CVSS v3.1 Published 2024-07-31
Fix available
A fix is available. Upgrade to 6.38.1-5 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
A verbose error handling issue in the proxy service implemented in the GravityZone Update Server allows an attacker to cause a server-side request forgery. This issue only affects GravityZone Console versions before 6.38.1-5 running only on premise.

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

A verbose error handling vulnerability in the GravityZone Update Server proxy service allows attackers to perform Server-Side Request Forgery (SSRF) attacks. This pre-authentication flaw affects on-premise GravityZone Console installations prior to version 6.38.1-5, potentially allowing attackers to make the server perform requests to arbitrary internal or external resources.

MitigationUpgrade GravityZone Console to version 6.38.1-5 or later to resolve the verbose error handling in the proxy service.

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.38.1-5

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. Confirm GravityZone Console installation type
    Identify whether the system is running an on-premise (self-hosted) GravityZone Console instance, as this vulnerability only affects on-premise deployments. Check installation documentation or consult your Bitdefender account representative.
    Affected if The environment is an on-premise (self-hosted) GravityZone Console installation.
  2. Locate the installed GravityZone Console version
    Access the GravityZone Console web interface and navigate to the About or System Information page, or check the installation files and documentation for the deployed version number.
    Affected if The installed version is lower than 6.38.1-5.
  3. Verify the Update Server proxy service is enabled
    Check the GravityZone Console configuration to determine if the Update Server proxy service is active. This is typically configured in the Update Services or Network Settings section of the console.
    Affected if The Update Server proxy service is enabled and the version is below 6.38.1-5.
  4. Review network exposure of the Update Server
    Examine network firewall rules and access controls to determine if the Update Server proxy service is accessible from untrusted networks or external IPs.
    Affected if The Update Server proxy service is network-accessible and the version is below 6.38.1-5.

A user is affected if they are running an on-premise GravityZone Console version below 6.38.1-5 with the Update Server proxy service enabled and exposed.

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.38.1-5 or later
Fixed in 6.38.1-5
Interim mitigation

Upgrade GravityZone Console to version 6.38.1-5 or later to resolve the verbose error handling in the proxy service.

Recommended fix High confidence

6.38.1-5

  1. 1. Back up your current GravityZone Console configuration and database before proceeding with the upgrade.
  2. 2. Download the GravityZone Console version 6.38.1-5 update package from the official Bitdefender download portal or your licensed vendor channel.
  3. 3. Apply the upgrade to your on-premise GravityZone Console installation following the standard Bitdefender upgrade procedure.
  4. 4. After the upgrade completes, verify that the GravityZone Console is running version 6.38.1-5.
  5. 5. Test that the Update Server proxy service is functioning correctly and that verbose error messages are no longer being exposed.
Caveat Review the GravityZone 6.38.1-5 release notes for any configuration or compatibility changes before upgrading.

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

Fix this in Gravityzone Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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