dbcve.org
Endpoint EncryptionApplication · Eset

CVE-2022-2402

MEDIUM · 6.5 CVSS v3.1 Published 2022-09-06
Fix available
A fix is available. Upgrade to 1.3.2.32 / 5.1.2.26 or later.
See remediation →
67/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
The vulnerability in the driver dlpfde.sys enables a user logged into the system to perform system calls leading to kernel stack overflow, resulting in a system crash, for instance, a BSOD.

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 · moderate confidence

A kernel stack overflow vulnerability in the dlpfde.sys driver allows any authenticated user to trigger the vulnerability through specific system calls, causing kernel stack overflow and resulting in a Blue Screen of Death (BSOD) system crash. This is a local denial-of-service vulnerability affecting the Windows kernel driver.

MitigationObtain and deploy an updated/patched version of the dlpfde.sys driver from the vendor, or if the driver is non-essential, remove or disable it to prevent exploitation.

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
Endpoint EncryptionApplication
Affected:< 5.1.2.26
Full Disk EncryptionApplication
Affected:< 1.3.2.32

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/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. Locate the dlpfde.sys driver file
    Search for dlpfde.sys on the system: open Command Prompt or PowerShell and run 'dir /s /b C:\Windows\System32\dlpfde.sys 2>nul' or use Get-ChildItem -Recurse -Path C:\Windows\System32\drivers -Filter dlpfde.sys
    Affected if The file exists on the system - the driver is present and may be vulnerable
  2. Retrieve the dlpfde.sys file version
    Right-click the driver file, select Properties, then Details tab, or run 'wmic datafile where "name='C:\\Windows\\System32\\drivers\\dlpfde.sys'" get Version,FileSize,LastModified' in Command Prompt
    Affected if The file version is lower than 5.1.2.26 (for Endpoint Encryption) or lower than 1.3.2.32 (for Full Disk Encryption)
  3. Check installed ESET Endpoint Encryption version
    Open Programs and Features (appwiz.cpl) or run 'Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -like "*ESET Endpoint Encryption*"} | Select-Object Name,Version' in PowerShell
    Affected if The installed version is shown but is lower than 5.1.2.26
  4. Check installed ESET Full Disk Encryption version
    Open Programs and Features or run 'Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -like "*ESET Full Disk Encryption*"} | Select-Object Name,Version' in PowerShell
    Affected if The installed version is shown but is lower than 1.3.2.32
  5. Verify if the driver is currently loaded
    Run 'sc query dlpfde' or 'driverquery /v | findstr dlpfde' in Command Prompt, or check Device Manager for hidden devices showing the driver
    Affected if The driver service state shows RUNNING or the driver appears in the loaded driver list - the vulnerability can be actively triggered

A user is affected if dlpfde.sys is present AND its file version or the installed ESET product version is below the patched versions (5.1.2.26 for Endpoint Encryption or 1.3.2.32 for Full Disk Encryption), especially if the driver is currently loaded.

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.

dbcve · scoped
Upgrade available Upgrade to 1.3.2.32 / 5.1.2.26 or later
Fixed in 1.3.2.325.1.2.26
Interim mitigation

Obtain and deploy an updated/patched version of the dlpfde.sys driver from the vendor, or if the driver is non-essential, remove or disable it to prevent exploitation.

Recommended fix Moderate confidence

Endpoint Encryption: 5.1.2.26 or later; Full Disk Encryption: 1.3.2.32 or later

  1. 1. Identify the ESET product installed (Endpoint Encryption or Full Disk Encryption) using the system's installed programs list
  2. 2. Back up all critical data and create a system restore point before proceeding with any update
  3. 3. Download the latest version of ESET Endpoint Encryption (5.1.2.26 or later) or Full Disk Encryption (1.3.2.32 or later) from the official ESET download page or your licensed ESET account
  4. 4. Verify the integrity of the downloaded installer using checksums if provided by ESET
  5. 5. Close all running applications and temporarily disable any active protection modules if required by the installer
  6. 6. Run the installer with administrative privileges and follow the on-screen prompts to complete the upgrade
  7. 7. Restart the system after installation completes to ensure the new driver (dlpfde.sys) is properly loaded
  8. 8. Verify the installed version matches the target version (5.1.2.26 or higher for Endpoint Encryption; 1.3.2.32 or higher for Full Disk Encryption)
Caveat Upgrading encryption software may require re-authentication or recovery key verification; ensure recovery media is available before proceeding

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Endpoint Encryption Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-2402 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2022-2402 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