dbcve.org
Antivirus PlusApplication · Bitdefender

CVE-2020-8107

HIGH · 7.8 CVSS v3.1 Published 2022-02-18
Fix available
A fix is available. Upgrade to 24.0.26.136 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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 Process Control vulnerability in ProductAgentUI.exe as used in Bitdefender Antivirus Plus allows an attacker to tamper with product settings via a specially crafted DLL file. This issue affects: Bitdefender Antivirus Plus versions prior to 24.0.26.136. Bitdefender Internet Security versions prior to 24.0.26.136. Bitdefender Total Security versions prior to 24.0.26.136.

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 Process Control vulnerability in Bitdefender's ProductAgentUI.exe allows attackers to tamper with product settings by planting a specially crafted malicious DLL file that gets loaded by the application. This DLL hijacking vulnerability enables privilege escalation and manipulation of antivirus settings.

MitigationUpgrade Bitdefender Antivirus Plus, Internet Security, or Total Security to version 24.0.26.136 or later to resolve the DLL loading vulnerability.

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
Antivirus PlusApplication
Affected:< 24.0.26.136
Internet SecurityApplication
Affected:< 24.0.26.136
Total SecurityApplication
Affected:< 24.0.26.136

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 Bitdefender product installation
    Open Control Panel > Programs and Features or use 'Get-WmiObject -Class Win32_Product' to list installed software and locate Bitdefender Antivirus Plus, Internet Security, or Total Security
    Affected if A Bitdefender Antivirus Plus, Internet Security, or Total Security product is listed in installed programs
  2. Determine installed Bitdefender version
    Locate the Bitdefender installation directory (commonly in Program Files or Program Files x86) and check the version of the ProductAgentUI.exe file, or right-click the executable and view Properties > Details for the File Version
    Affected if The ProductAgentUI.exe file version is below 24.0.26.136
  3. Verify vulnerable executable exists
    Search for ProductAgentUI.exe in the Bitdefender installation folder (typically under Program Files/Bitdefender or similar path) and confirm its presence
    Affected if ProductAgentUI.exe exists and runs with elevated privileges in the environment
  4. Check current process status
    Open Task Manager or use 'Get-Process' in PowerShell to check if ProductAgentUI.exe is currently running
    Affected if ProductAgentUI.exe is actively running on the system

A user is affected if Bitdefender Antivirus Plus, Internet Security, or Total Security is installed with ProductAgentUI.exe version below 24.0.26.136, enabling a DLL hijacking attack that could manipulate antivirus settings.

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

Upgrade Bitdefender Antivirus Plus, Internet Security, or Total Security to version 24.0.26.136 or later to resolve the DLL loading vulnerability.

Recommended fix High confidence

Bitdefender Antivirus Plus, Internet Security, or Total Security version 24.0.26.136

  1. Verify current Bitdefender product version by opening the Bitdefender interface and navigating to Settings > About
  2. Download Bitdefender version 24.0.26.136 or later from the official Bitdefender website at www.bitdefender.com
  3. Run the downloaded installer and follow the on-screen prompts to upgrade the product
  4. Restart the computer if prompted by the installer
  5. Verify the upgrade was successful by checking the version number in Settings > About

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

Fix this in Antivirus Plus Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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