Antivirus PlusApplication · Bitdefender

CVE-2019-14242

MEDIUM · 6.7 CVSS v3.0 Published 2019-07-30
Fix available
A fix is available. Upgrade to 6.6.8.115 / 23.0.24.120 or later.
See remediation →
69/100
Remediation priority · Elevated
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
An issue was discovered in Bitdefender products for Windows (Bitdefender Endpoint Security Tool versions prior to 6.6.8.115; and Bitdefender Antivirus Plus, Bitdefender Internet Security, and Bitdefender Total Security versions prior to 23.0.24.120) that can lead to local code injection. A local attacker with administrator privileges can create a malicious DLL file in %SystemRoot%\System32\ that will be executed with local user privileges.

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 DLL hijacking vulnerability in Bitdefender products for Windows allows a local attacker with administrator privileges to place a malicious DLL in %SystemRoot%\System32\, which gets loaded and executed by Bitdefender components with local user privileges. This enables code injection and potential privilege persistence.

MitigationUpgrade Bitdefender Endpoint Security Tool to version 6.6.8.115 or later, and consumer products (Antivirus Plus, Internet Security, Total Security) to version 23.0.24.120 or later. Apply the vendor patches through standard Bitdefender update mechanisms.

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:< 23.0.24.120
Endpoint Security ToolApplication
Affected:< 6.6.8.115
Internet SecurityApplication
Affected:< 23.0.24.120
Total SecurityApplication
Affected:< 23.0.24.120

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

CVSS:3.0/AV:L/AC:L/PR:H/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 installed Bitdefender product and version
    Open Control Panel > Programs and Features, or run 'Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -like "*Bitdefender*"}' in PowerShell to list installed Bitdefender products with their version numbers.
    Affected if The installed version falls below 23.0.24.120 for consumer products (Antivirus Plus, Internet Security, Total Security) or below 6.6.8.115 for Bitdefender Endpoint Security Tool.
  2. Confirm Bitdefender services are present
    Open Services (services.msc) and look for Bitdefender-related services such as 'Bitdefender Endpoint Security Agent', 'Bitdefender Antivirus', or check via command: 'Get-Service | Where-Object {$_.DisplayName -like "*Bitdefender*"}'
    Affected if Bitdefender services are running on the system, indicating the vulnerable software is active and could be exploited.
  3. Verify user privileges on the system
    Check if standard or low-privilege users have access to the system. Run 'whoami /all' to see your current privileges and 'net user' to enumerate local users.
    Affected if An administrator-level account could place a malicious DLL in %SystemRoot%\System32\, which would then be loaded by Bitdefender components running under lower-privilege user contexts.

You are affected if a Bitdefender product (Antivirus Plus, Internet Security, Total Security, or Endpoint Security Tool) is installed with a version below the safe thresholds (23.0.24.120 or 6.6.8.115) and the system has multiple user accounts where an administrator could perform DLL hijacking.

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
Upgrade available Upgrade to 6.6.8.115 / 23.0.24.120 or later
Fixed in 6.6.8.11523.0.24.120
Interim mitigation

Upgrade Bitdefender Endpoint Security Tool to version 6.6.8.115 or later, and consumer products (Antivirus Plus, Internet Security, Total Security) to version 23.0.24.120 or later. Apply the vendor patches through standard Bitdefender update mechanisms.

Fix this in Antivirus Plus Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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