CVE-2019-17100
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 · uneditedAn Untrusted Search Path vulnerability in bdserviceshost.exe as used in Bitdefender Total Security 2020 allows an attacker to execute arbitrary code. This issue does not affect: Bitdefender Total Security versions prior to 24.0.12.69.
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 confidenceAn untrusted search path vulnerability in bdserviceshost.exe allows an attacker to execute arbitrary code by potentially loading malicious DLLs from attacker-controlled locations. This service host process in Bitdefender Total Security 2020 does not properly validate DLL search paths before loading libraries.
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< 24.0.12.69CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Bitdefender Total Security 2020 is installedCheck the installed programs list in Windows Settings > Apps & Features, or query the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry named 'Bitdefender Total Security'Affected if The product is listed as installed and shows as version 24.0.12.68 or earlier
-
Locate the vulnerable bdserviceshost.exe componentNavigate to the Bitdefender installation directory (commonly C:\Program Files\Bitdefender\Bitdefender Security\ or C:\Program Files\Bitdefender\Total Security\) and verify that bdserviceshost.exe exists in that folderAffected if The file bdserviceshost.exe is present in the Bitdefender installation directory
-
Verify the installed version numberRight-click on bdserviceshost.exe, select Properties, and check the File Version on the Details tab. Alternatively, right-click the main Bitdefender icon in the system tray and select 'About' to view the product versionAffected if The reported version is below 24.0.12.69 (for example, 24.0.12.68, 24.0.12.45, or any 24.0.x version prior to 24.0.12.69)
-
Confirm the service is registered in WindowsOpen Services.msc and look for a service named 'Bitdefender' or 'Bitdefender Security Service' that uses bdserviceshost.exe as its executable, or run 'sc query' from an elevated command prompt to enumerate Bitdefender-related servicesAffected if A Bitdefender service using bdserviceshost.exe is registered and running on the system
The environment is affected if Bitdefender Total Security 2020 is installed with any version prior to 24.0.12.69 and the bdserviceshost.exe component is present on the system.
Generated from the published advisory. Verify against your own configuration.
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 data24.0.12.69
Upgrade Bitdefender Total Security 2020 to version 24.0.12.69 or later to apply the vendor patch.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-17100 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-17100 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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