dbcve.org
Total SecurityApplication · Gdata Software

CVE-2024-30377

HIGH · 7.8 CVSS v3.1 Published 2024-11-22
Fix available
A fix is available. Upgrade to 25.5.18.333 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
G DATA Total Security Scan Server Link Following Local Privilege Escalation Vulnerability. This vulnerability allows local attackers to escalate privileges on affected installations of G DATA Total Security. An attacker must first obtain the ability to execute low-privileged code on the target system in order to exploit this vulnerability. The specific flaw exists within the G DATA AntiVirus Scan Server. By creating a symbolic link, an attacker can abuse the service to delete arbitrary files. An attacker can leverage this vulnerability to escalate privileges and execute arbitrary code in the context of SYSTEM. Was ZDI-CAN-23381.

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 link following vulnerability in the G DATA AntiVirus Scan Server allows local attackers to create symbolic links that abuse the service to delete arbitrary files. By leveraging this file deletion capability, an attacker can escalate privileges from low-privileged code execution to SYSTEM context and achieve arbitrary code execution.

MitigationApply the vendor patch for CVE-2024-30377 when available. Until then, restrict local code execution privileges and monitor the Scan Server service for suspicious symlink operations.

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
Total SecurityApplication
Affected:< 25.5.18.333

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. Identify G DATA software installation and version
    Open Windows Control Panel > Programs and Features, or run: Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object {$_.DisplayName -like '*G DATA*'} | Select-Object DisplayName, DisplayVersion
    Affected if G DATA Total Security is installed with a version lower than 25.5.18.333
  2. Verify Scan Server service status
    Open Services.msc and locate 'G DATA AntiVirus Scan Server' service, or run: Get-Service -Name '*GDATA*Scan*' 2>$null
    Affected if The Scan Server service exists and is running (vulnerability requires this service to be active)
  3. Confirm affected version range
    Compare the installed DisplayVersion from step 1 against the affected range: any version below 25.5.18.333 is vulnerable
    Affected if Installed version is 25.5.18.332 or lower

You are affected if G DATA Total Security is installed with the Scan Server service running and the version is below 25.5.18.333.

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 25.5.18.333 or later
Fixed in 25.5.18.333
Interim mitigation

Apply the vendor patch for CVE-2024-30377 when available. Until then, restrict local code execution privileges and monitor the Scan Server service for suspicious symlink operations.

Recommended fix High confidence

G DATA Total Security 25.5.18.333 or later

  1. 1. Verify current G DATA Total Security version by opening the application and checking 'About' or 'Help' section
  2. 2. Download G DATA Total Security version 25.5.18.333 or later from the official G DATA website (www.gdata.com)
  3. 3. Ensure you have administrator privileges on the target system
  4. 4. Close any running instances of G DATA Total Security
  5. 5. Run the installer and follow the on-screen prompts to upgrade the software
  6. 6. After installation, verify the new version is installed correctly
  7. 7. Restart the system to ensure all services load with the updated version

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

Fix this in Total Security Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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