CVE-2022-0357
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 · uneditedUnquoted Search Path or Element vulnerability in the Vulnerability Scan component of Bitdefender Total Security, Bitdefender Internet Security, and Bitdefender Antivirus Plus allows an attacker to elevate privileges to SYSTEM. This issue affects: Bitdefender Total Security versions prior to 26.0.10.45. Bitdefender Internet Security versions prior to 26.0.10.45. Bitdefender Antivirus Plus versions prior to 26.0.10.45.
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 the Bitdefender Vulnerability Scan service where the executable path contains spaces and is not enclosed in quotes. An attacker with low-privilege access can place a malicious executable in an intermediate directory within the unquoted path (e.g., 'C:\Program Files\Bitdefender\Some Tool\service.exe') which Windows will attempt to execute before the actual service binary, resulting in SYSTEM-level code execution.
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< 26.0.10.45< 26.0.10.45< 26.0.10.45CVSS 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.
-
Query the Bitdefender Vulnerability Scan service binary pathOpen Command Prompt as Administrator and run: sc qc "Vulnerability Scan" (or look for a service with 'Vulnerability' or 'Bitdefender' in the name using: sc queryex type= service state= all | findstr /i "vulnerability bitdefender")Affected if The displayed BINARY_PATH_NAME contains spaces and is not enclosed in quotation marks (e.g., C:\Program Files\Bitdefender\Some Tool\service.exe instead of "C:\Program Files\Bitdefender\Some Tool\service.exe")
-
Identify installed Bitdefender product and version from registryOpen Registry Editor and check: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ for a key with DisplayName containing "Bitdefender" (such as "Bitdefender Antivirus Plus", "Bitdefender Internet Security", or "Bitdefender Total Security"). Read the DisplayVersion value from that key.Affected if The DisplayVersion value is lower than 26.0.10.45 (e.g., 26.0.8.30, 25.0.x.x, etc.)
-
Alternative version check via file propertiesLocate the main Bitdefender executable (typically in C:\Program Files\Bitdefender\Bitdefender Security\ or C:\Program Files\Bitdefender\AntiVirus\), right-click the main .exe file, select Properties, and view the File version on the Details tab.Affected if The file version shown is lower than 26.0.10.45
The environment is affected if the Bitdefender Vulnerability Scan service has an unquoted binary path AND the installed Bitdefender product version is below 26.0.10.45.
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 · scoped26.0.10.45
Apply vendor patch version 26.0.10.45 or later to Bitdefender Total Security, Internet Security, or Antivirus Plus installations to remediate the unquoted service path vulnerability.
26.0.10.45
- Open Bitdefender application on the affected system
- Navigate to the Settings or Update section
- Check for updates and ensure the product is updated to version 26.0.10.45 or later
- Alternatively, download the latest installer from www.bitdefender.com and reinstall to ensure version 26.0.10.45 or later is installed
- Verify the installed version matches or exceeds 26.0.10.45
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.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,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-0357 — 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-0357 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