CVE-2021-3579
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 · uneditedIncorrect Default Permissions vulnerability in the bdservicehost.exe and Vulnerability.Scan.exe components as used in Bitdefender Endpoint Security Tools for Windows, Total Security allows a local attacker to elevate privileges to NT AUTHORITY\SYSTEM This issue affects: Bitdefender Endpoint Security Tools for Windows versions prior to 7.2.1.65. Bitdefender Total Security versions prior to 7.2.1.65.
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 confidenceThis is a local privilege escalation vulnerability in Bitdefender Endpoint Security Tools and Total Security for Windows. The bdservicehost.exe and Vulnerability.Scan.exe components have incorrect default file/folder permissions that allow a local authenticated attacker to manipulate executables or configuration paths to gain NT AUTHORITY\SYSTEM privileges.
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< 7.2.1.65< 7.2.1.65CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Bitdefender productsOpen Programs and Features in Control Panel or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion' via PowerShell to list installed softwareAffected if Neither Bitdefender Endpoint Security Tools nor Bitdefender Total Security appears in the installed programs list
-
Check Bitdefender Endpoint Security Tools versionCheck the installation directory (typically C:\Program Files\Bitdefender\Endpoint Security\) for bdservicehost.exe, right-click the file, select Properties, and view the Details tab for the version numberAffected if Version is present but lower than 7.2.1.65
-
Check Bitdefender Total Security versionCheck the installation directory (typically C:\Program Files\Bitdefender\Total Security\) for Vulnerability.Scan.exe, right-click the file, select Properties, and view the Details tab for the version numberAffected if Version is present but lower than 7.2.1.65
-
Verify vulnerable components existNavigate to the Bitdefender installation directories and confirm bdservicehost.exe and Vulnerability.Scan.exe files are present using Windows Explorer or command 'dir C:\Program Files\Bitdefender\*\*.exe'Affected if Either bdservicehost.exe or Vulnerability.Scan.exe exists in the installation folder
-
Inspect file permissions on vulnerable executablesRight-click bdservicehost.exe or Vulnerability.Scan.exe, select Properties, go to the Security tab, and verify which users have Write or Modify permissions on the file or its containing folderAffected if Authenticated users or non-admin accounts have Write or Modify permissions to the executables or their parent directories
A user is affected if either Bitdefender Endpoint Security Tools or Total Security is installed with a version lower than 7.2.1.65 and the vulnerable executables exist with overly permissive file access controls.
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.
dbcve · scoped7.2.1.65
Upgrade to Bitdefender Endpoint Security Tools or Total Security version 7.2.1.65 or later to obtain the patched binaries with correct permissions.
7.2.1.65 or later
- Download Bitdefender Endpoint Security Tools for Windows version 7.2.1.65 or later from the official Bitdefender website (www.bitdefender.com)
- Download Bitdefender Total Security version 7.2.1.65 or later from the official Bitdefender website (www.bitdefender.com)
- Install the updated version on affected systems to remediate the incorrect default permissions vulnerability in bdservicehost.exe and Vulnerability.Scan.exe components
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-3579 — 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-2021-3579 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