dbcve.org
Cyber SecurityApplication · Eset

CVE-2020-10180

CRITICAL · 9.8 CVSS v3.1 Published 2020-03-05
Fix available
A fix is available. Upgrade to 1294 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 ESET AV parsing engine allows virus-detection bypass via a crafted BZ2 Checksum field in an archive. This affects versions before 1294 of Smart Security Premium, Internet Security, NOD32 Antivirus, Cyber Security Pro (macOS), Cyber Security (macOS), Mobile Security for Android, Smart TV Security, and NOD32 Antivirus 4 for Linux Desktop.

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's antivirus parsing engine contains a flaw where a crafted BZ2 archive with a malformed Checksum field can evade virus detection. This parsing logic vulnerability allows malicious payloads to bypass security scanning in affected versions before 1294.

MitigationUpdate all affected ESET products (Smart Security Premium, Internet Security, NOD32 Antivirus, Cyber Security, Mobile Security for Android, Smart TV Security, NOD32 Antivirus 4 for Linux) to version 1294 or later to remediate this vulnerability.

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
Cyber SecurityApplication
Affected:< 1294
Mobile SecurityApplication
Affected:< 1294
Nod32 AntivirusApplication
Affected:< 1294= 4
Smart SecurityApplication
Affected:< 1294
Smart Tv SecurityApplication
Affected:< 1294

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify installed ESET product
    Open the ESET application or check installed programs list to determine which ESET product is installed (Cyber Security, Mobile Security, NOD32 Antivirus, Smart Security, or Smart TV Security)
    Affected if Any of these products are installed and version is below 1294 (or exactly version 4 for NOD32 Antivirus)
  2. Check installed ESET version number
    Open the ESET product interface, go to Help and Support or About section, or run the command 'eset --version' if available, to find the exact version number
    Affected if Version number cannot be determined or is less than 1294 (or exactly version 4 for NOD32)
  3. Compare version against affected ranges
    Compare your installed version to the affected ranges: Cyber Security < 1294, Mobile Security < 1294, NOD32 Antivirus < 1294 or = 4, Smart Security < 1294, Smart TV Security < 1294
    Affected if Your installed version falls within any of these affected ranges
  4. Confirm scanning module is active
    Check that real-time file system monitoring or scheduled scans are enabled in the ESET product settings (this is required for the vulnerability to be exploitable)
    Affected if Real-time protection or scheduled scans are enabled and the version is affected

You are affected if any ESET product from the list is installed with a version number below 1294 (or exactly version 4 for NOD32 Antivirus) and scanning features are active.

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 1294 or later
Fixed in 1294
Interim mitigation

Update all affected ESET products (Smart Security Premium, Internet Security, NOD32 Antivirus, Cyber Security, Mobile Security for Android, Smart TV Security, NOD32 Antivirus 4 for Linux) to version 1294 or later to remediate this vulnerability.

Recommended fix High confidence

Version 1294 or later for all affected ESET products (Cyber Security, Mobile Security, NOD32 Antivirus, Smart Security, Smart TV Security)

  1. 1. Identify the installed ESET product (Cyber Security, Mobile Security, NOD32 Antivirus, Smart Security, or Smart TV Security)
  2. 2. Check the current version of the installed ESET product
  3. 3. If the version is below 1294, initiate an upgrade to version 1294 or later
  4. 4. Verify the upgrade was successful by checking the new version number
  5. 5. Ensure virus definition databases are updated after the upgrade
Caveat Standard ESET upgrade; enterprise configurations should be reviewed for compatibility with the new version

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

Fix this in Cyber Security Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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