dbcve.org
Endpoint AntivirusApplication · Eset

CVE-2021-37852

HIGH · 7.8 CVSS v3.1 Published 2022-02-09
Fix available
A fix is available. Upgrade to 7.3.2055.0 / 7.3.10014.0 or later.
See remediation →
80/100
Remediation priority · High
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
ESET products for Windows allows untrusted process to impersonate the client of a pipe, which can be leveraged by attacker to escalate privileges in the context of NT AUTHORITY\SYSTEM.

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 confidence

ESET security products for Windows contain a named pipe impersonation vulnerability where an untrusted local process can impersonate the client of a communication pipe used by ESET's services, allowing local privilege escalation to NT AUTHORITY\SYSTEM context.

MitigationApply the vendor patch or update ESET products to the latest version that addresses CVE-2021-37852.

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 AntivirusApplication
Affected:>= 6.6.2046.0, < 7.3.2055.0>= 8.0, < 8.0.2028.3>= 8.1, < 8.1.2031.4>= 9.0, < 9.0.2032.6
Endpoint SecurityApplication
Affected:>= 6.6.2046.0, < 7.3.2055.0>= 8.0, < 8.0.2028.3>= 8.1, < 8.1.2031.4>= 9.0, < 9.0.2032.6
File SecurityApplication
Affected:>= 7.0.12014.0, <= 7.3.12006.0
Internet SecurityApplication
Affected:>= 10.0.337.1, < 15.0.18.0
Mail SecurityApplication
Affected:>= 7.0.10019, < 7.3.10014.0>= 7.0.14008.0, < 7.3.14003.0>= 8.0, < 8.0.14006.0>= 8.0.10012.0, < 8.0.10018.0
Nod32 AntivirusApplication
Affected:>= 10.0.337.1, <= 15.0.18.0
SecurityApplication
Affected:>= 7.0.15008.0, <= 8.0.15004.0
Server SecurityApplication
Affected:>= 7.0.12016.1002, <= 7.2.12004.1000= 8.0.12003.0= 8.0.12003.1

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm ESET product is installed
    Open Control Panel > Programs and Features, or check Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ for entries starting with 'ESET', or look for ESET processes in Task Manager
    Affected if Any ESET security product is found on the system
  2. Identify the specific ESET product and version
    In Programs and Features, note the exact product name (e.g., ESET Endpoint Antivirus, ESET NOD32 Antivirus) and its installed version number shown in the Version column
    Affected if Product name matches any of the affected products listed in the CVE
  3. Compare version against affected ranges for Endpoint products
    For Endpoint Antivirus or Endpoint Security, compare your version to: 6.6.2046.0 to <7.3.2055.0; 8.0 to <8.0.2028.3; 8.1 to <8.1.2031.4; or 9.0 to <9.0.2032.6
    Affected if Your installed version falls within any of these range pairs
  4. Compare version against affected ranges for consumer products
    For Internet Security or NOD32 Antivirus, compare to: >=10.0.337.1 and <=15.0.18.0. For Mail Security, check multiple ranges: 7.0.10019 to <7.3.10014.0; >=7.0.14008.0 to <7.3.14003.0; 8.0 to <8.0.14006.0; >=8.0.10012.0 to <8.0.10018.0
    Affected if Your installed version falls within any of these range pairs
  5. Compare version against affected ranges for File and Server Security
    For File Security, check if version is >=7.0.12014.0 and <=7.3.12006.0. For Server Security, check if version is >=7.0.12016.1002 to <=7.2.12004.1000, or equals 8.0.12003.0 or 8.0.12003.1
    Affected if Your installed version falls within these specific ranges

You are affected if any ESET product from the list is installed and its installed version number falls within one of the version ranges specified for that product.

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 7.3.2055.0 / 7.3.10014.0 / 7.3.14003.0 or later
Fixed in 7.3.2055.07.3.10014.07.3.14003.0
Interim mitigation

Apply the vendor patch or update ESET products to the latest version that addresses CVE-2021-37852.

Recommended fix High confidence

Upgrade to ESET version 7.3.2055.0 or later for v6.6 products; 8.0.2028.3 or later for v8.0 products; 8.1.2031.4 or later for v8.1 products; 9.0.2032.6 or later for v9.0 products; 15.0.18.0 or later for v10.0+ products; or the appropriate latest 7.3.x release for File Security and Mail Security prod

  1. 1. Identify the specific ESET product and current version installed using the system's installed programs or ESET's About dialog
  2. 2. Determine the product family (Endpoint Antivirus, Endpoint Security, File Security, Internet Security, Mail Security, Nod32 Antivirus, Security, or Server Security)
  3. 3. Navigate to the official ESET support portal at support.eset.com to download the latest version for your product line
  4. 4. Download the fixed version that meets or exceeds: 7.3.2055.0 for v6.6 products; 8.0.2028.3 for v8.0 products; 8.1.2031.4 for v8.1 products; 9.0.2032.6 for v9.0 products; 15.0.18.0 for v10.0+ Internet Security/Nod32; or the appropriate 7.3.xx version for File Security/Mail Security
  5. 5. Ensure you have administrative privileges on the Windows system
  6. 6. Disable real-time protection temporarily if prompted during installation
  7. 7. Run the ESET installer with administrator privileges
  8. 8. Follow the on-screen installation prompts to complete the upgrade
Caveat Upgrading between major versions may require reconfiguration of custom scan exclusions or policy settings; ensure backup of current configuration before upgrading

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

Fix this in Endpoint Antivirus Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-37852 — 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-2021-37852 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