CVE-2022-3369
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 Improper Access Control vulnerability in the bdservicehost.exe component, as used in Bitdefender Engines for Windows, allows an attacker to delete privileged registry keys by pointing a Registry symlink to a privileged key. This issue affects: Bitdefender Engines versions prior to 7.92659. It also affects Bitdefender Antivirus Free, Bitdefender Antivirus Plus, Bitdefender Internet Security, Bitdefender Total Security, as well as Bitdefender Endpoint Security Tools for Windows with engine versions prior to 7.92659.
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 confidenceImproper Access Control vulnerability in the bdservicehost.exe component of Bitdefender Engines for Windows allows a local attacker to delete privileged registry keys by exploiting registry symlinks. This is a local privilege tampering issue affecting engine versions prior to 7.92659.
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.92659CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
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.
-
Verify Bitdefender installationCheck if any Bitdefender product (Antivirus Free, Antivirus Plus, Internet Security, Total Security, or Endpoint Security Tools for Windows) is installed on the system via Programs and Features or the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\UninstallAffected if No Bitdefender product is installed, the system is not affected by this specific vulnerability
-
Locate the Bitdefender engine componentSearch for bdservicehost.exe in the Bitdefender installation directory (typically under C:\Program Files\Bitdefender or C:\Program Files (x86)\Bitdefender)Affected if bdservicehost.exe is not found, the vulnerable component is not present
-
Identify the Bitdefender engine versionRight-click bdservicehost.exe, select Properties, and view the File Version on the Details tab, or use the command: wmic datafile where "name='C:\\Program Files\\Bitdefender\\bdservicehost.exe'" get VersionAffected if The file version cannot be determined or retrieved, manual version lookup is required
-
Compare installed version against the affected rangeCompare the identified engine version number to 7.92659 - any version lower than 7.92659 falls within the affected rangeAffected if The installed engine version is lower than 7.92659, the system is vulnerable to this privilege tampering issue
-
Confirm the attack vector requires local accessRecognize that this is a local privilege tampering vulnerability requiring an authenticated attacker with the ability to execute code on the target systemAffected if Remote unauthenticated exploitation is not applicable to this specific CVE
A system is affected if it runs any Bitdefender product for Windows with an engine version lower than 7.92659 where the bdservicehost.exe component is present.
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.92659
Update Bitdefender engine versions to 7.92659 or later, or apply vendor-supplied security patches to all affected products including Antivirus Free, Antivirus Plus, Internet Security, Total Security, and Endpoint Security Tools for Windows.
Bitdefender Engines version 7.92659 or later (for all affected products including Antivirus Free, Antivirus Plus, Internet Security, Total Security, and Endpoint Security Tools)
- Identify the specific Bitdefender product installed (Antivirus Free, Antivirus Plus, Internet Security, Total Security, or Endpoint Security Tools)
- Open the Bitdefender interface and navigate to the Updates or Settings section
- Check the current engine version to confirm it is below 7.92659
- Initiate an update to download the latest engine version (7.92659 or later)
- Restart the system if prompted by the update process
- Verify the engine version has been updated to 7.92659 or higher by checking the Updates section or viewing the engine details
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-3369 — 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-2022-3369 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