Link Following (Symlink)Weakness · CWE-59

CVE-2024-13759

HIGH · 7.8 CVSS v3.1 Published 2025-05-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Local Privilege Escalation in Avira.Spotlight.Service.exe in Avira Prime 1.1.96.2 on Windows 10 x64  allows local attackers to gain system-level privileges via arbitrary file deletion

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

The vulnerability exists in Avira.Spotlight.Service.exe, a Windows service component of Avira Prime 1.1.96.2. A local attacker with limited Windows user privileges can exploit an arbitrary file deletion flaw in this service to escalate to system-level privileges, likely by deleting critical files or exploiting file handling to manipulate service execution context.

MitigationApply vendor-supplied patch or upgrade Avira Prime to a version that addresses CVE-2024-13759; until then, limit local user access and monitor the service binary for unauthorized modification or suspicious file operations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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. Verify Avira Prime installation
    Check for Avira Prime by looking for the service 'Avira Spotlight Service' in Windows Services (services.msc), or check the installation directory typically at C:\Program Files\Avira\ or C:\Program Files (x86)\Avira\
    Affected if Avira Prime is installed and the Avira.Spotlight.Service service exists in Windows Services
  2. Check Avira.Spotlight.Service.exe version
    Locate the file Avira.Spotlight.Service.exe (commonly in C:\Program Files\Avira\Spotlight\ or C:\Program Files (x86)\Avira\Spotlight\) and right-click to view Properties, then check the Details tab for Product Version, or run: Get-Item 'C:\Program Files\Avira\Spotlight\Avira.Spotlight.Service.exe' | Select-Object VersionInfo
    Affected if The product version is 1.1.96.2 or any version lower than the patched version
  3. Confirm the Avira Spotlight Service is present
    Open Services (services.msc) and locate 'Avira Spotlight Service', or run: Get-Service -Name 'Avira Spotlight Service' -ErrorAction SilentlyContinue
    Affected if The service named 'Avira Spotlight Service' exists and is registered on the system
  4. Verify file permissions on the service binary
    Right-click Avira.Spotlight.Service.exe, go to Properties > Security tab, or run: icacls 'C:\Program Files\Avira\Spotlight\Avira.Spotlight.Service.exe' to list all user/group permissions
    Affected if Non-admin users have Write or Full Control permissions on the service executable, enabling potential file manipulation
  5. Check service binary location and integrity
    Verify the service executable exists at the expected path and has not been tampered with by comparing its hash, or check if the file is in a user-writable directory
    Affected if The service binary is missing from its expected installation directory or resides in a location with weak access controls

A user is affected if Avira Prime with Avira.Spotlight.Service version 1.1.96.2 or lower is installed and the service is present on the system.

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 patch or upgrade Avira Prime to a version that addresses CVE-2024-13759; until then, limit local user access and monitor the service binary for unauthorized modification or suspicious file operations.

Have this fixed 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 help mitigating

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-13759 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-13759 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