dbcve.org
Endpoint AntivirusApplication · Eset

CVE-2022-27167

HIGH · 7.1 CVSS v3.1 Published 2022-05-10
Fix available
A fix is available. Upgrade to 8.0.2053.0 / 8.0.10020.0 or later.
See remediation →
73/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
Privilege escalation vulnerability in Windows products of ESET, spol. s r.o. allows attacker to exploit "Repair" and "Uninstall" features what may lead to arbitrary file deletion. This issue affects: ESET, spol. s r.o. ESET NOD32 Antivirus 11.2 versions prior to 15.1.12.0. ESET, spol. s r.o. ESET Internet Security 11.2 versions prior to 15.1.12.0. ESET, spol. s r.o. ESET Smart Security Premium 11.2 versions prior to 15.1.12.0. ESET, spol. s r.o. ESET Endpoint Antivirus 6.0 versions prior to 9.0.2046.0. ESET, spol. s r.o. ESET Endpoint Security 6.0 versions prior to 9.0.2046.0. ESET, spol. s r.o. ESET Server Security for Microsoft Windows Server 8.0 versions prior to 9.0.12012.0. ESET, spol. s r.o. ESET File Security for Microsoft Windows Server 8.0.12013.0. ESET, spol. s r.o. ESET Mail Security for Microsoft Exchange Server 6.0 versions prior to 8.0.10020.0. ESET, spol. s r.o. ESET Mail Security for IBM Domino 6.0 versions prior to 8.0.14011.0. ESET, spol. s r.o. ESET Security for Microsoft SharePoint Server 6.0 versions prior to 8.0.15009.0.

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 Windows products contain a privilege escalation vulnerability where the 'Repair' and 'Uninstall' features can be exploited to achieve arbitrary file deletion. An attacker with local access to a system running vulnerable ESET software can elevate privileges by manipulating these repair/uninstall operations.

MitigationUpdate ESET products to the patched versions specified in the advisory (15.1.12.0 for consumer/office products, 9.0.2046.0 for Endpoint 6.x, 9.0.12012.0 for Server Security, and respective patches for Exchange/SharePoint/Domino versions).

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.0, < 8.0.2053.0>= 8.1, < 8.1.2050.0>= 9.0, < 9.0.2046.0
Endpoint SecurityApplication
Affected:>= 6.0, < 8.0.2053.0>= 8.1, < 8.1.2050.0>= 9.0, < 9.0.2046.0
File SecurityApplication
Affected:>= 6.0, < 8.0.12013.0
Internet SecurityApplication
Affected:>= 11.2, < 15.1.12.0
Mail SecurityApplication
Affected:>= 6.0, < 8.0.10020.0>= 6.0, < 8.0.14011.0
Nod32 AntivirusApplication
Affected:>= 11.2, < 15.1.12.0
SecurityApplication
Affected:>= 6.0, < 8.0.15009.0
Server SecurityApplication
Affected:>= 6.0>= 8.0, < 9.0.12012.0

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
None
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/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. Identify installed ESET product
    Open Control Panel > Programs and Features, or check registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ for entries starting with 'ESET', to determine which ESET product is installed
    Affected if Any ESET product from the affected list is installed (Endpoint Antivirus, Endpoint Security, File Security, Internet Security, Mail Security, Nod32 Antivirus, Security, or Server Security)
  2. Find installed ESET version
    In Programs and Features, click on the ESET product and view the Version column, or check the Version value in the product's registry uninstall key
    Affected if Version cannot be determined or is below the patched releases
  3. Compare version against affected ranges
    Match your installed product and version against the affected ranges: Endpoint Antivirus/Security: < 8.0.2053.0 (6.x), < 8.1.2050.0 (8.1.x), < 9.0.2046.0 (9.x); File Security: < 8.0.12013.0; Internet Security/Nod32: < 15.1.12.0; Mail Security: < 8.0.10020.0 or < 8.0.14011.0; Security: < 8.0.15009.0; Server Security: < 9.0.12012.0
    Affected if Installed version falls within any of the vulnerable version ranges for the detected product
  4. Verify repair/uninstall functionality exists
    Confirm that the ESET product's repair and uninstall options are available (check Start Menu shortcuts for the ESET product, or look for repair option in Programs and Features)
    Affected if Repair and uninstall features are present, which they are by default in vulnerable versions

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 8.0.2053.0 / 8.0.10020.0 / 8.0.12013.0 or later
Fixed in 8.0.2053.08.0.10020.08.0.12013.0
Interim mitigation

Update ESET products to the patched versions specified in the advisory (15.1.12.0 for consumer/office products, 9.0.2046.0 for Endpoint 6.x, 9.0.12012.0 for Server Security, and respective patches for Exchange/SharePoint/Domino versions).

Recommended fix High confidence

Upgrade to the minimum fixed version for your product line: Endpoint products to 9.0.2046.0 (or 8.0.2053.0/8.1.2050.0 for older branches), Internet Security/Nod32 Antivirus to 15.1.12.0, File Security to 8.0.12013.0, Server Security to 9.0.12012.0, Mail Security to 8.0.10020.0 or 8.0.14011.0, ShareP

  1. Identify the current version of the installed ESET product using the application's About or version information
  2. Download the appropriate fixed version from official ESET channels (support.eset.com or eset.com)
  3. Close any applications that may interfere with the installation
  4. Run the ESET installer for the fixed version (e.g., Endpoint Antivirus 9.0.2046.0 or higher, Endpoint Security 9.0.2046.0 or higher, Internet Security 15.1.12.0 or higher, Nod32 Antivirus 15.1.12.0 or higher)
  5. Follow the on-screen prompts to complete the installation
  6. Verify the installation was successful by checking the product version
  7. Restart the system if prompted by the installer
Caveat Review ESET release notes for your specific product version to check for any feature changes or compatibility considerations before upgrading

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

Fix this in Endpoint Antivirus Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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