dbcve.org
Nod32 AntivirusApplication · Eset

CVE-2020-10193

HIGH · 7.5 CVSS v3.1 Published 2020-03-06
Fix available
A fix is available. Upgrade to 4 / 1294 or later.
See remediation →
84/100
Remediation priority · High
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
ESET Archive Support Module before 1294 allows virus-detection bypass via crafted RAR Compression Information 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

The ESET Archive Support Module before version 1294 contains a vulnerability that allows malware to evade detection by embedding malicious code within crafted RAR Compression Information structures in archive files. This bypass affects the virus-scanning engine's ability to detect threats in compressed RAR archives.

MitigationUpdate all affected ESET products (Smart Security Premium, Internet Security, NOD32 Antivirus, Cyber Security Pro, Cyber Security, Mobile Security for Android, Smart TV Security, and NOD32 Antivirus 4 for Linux Desktop) to version 1294 or later of the Archive Support Module.

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
Nod32 AntivirusApplication
Affected:< 4< 1294
Cyber SecurityApplication
Affected:< 1294
Internet SecurityApplication
Affected:< 1294
Mobile SecurityApplication
Affected:< 1294= 1294
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
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

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
    Check if any ESET security product (NOD32 Antivirus, Internet Security, Smart Security, Cyber Security, Mobile Security, Smart TV Security) is installed on the system. On Windows, open the ESET application and go to Help > About. On macOS, check System Preferences > Security & Privacy or the ESET app About section. On Android, check Apps > ESET app > App info. On Linux, run 'esets_daemon -v' or check installed packages.
    Affected if An ESET product is installed and running on the system.
  2. Locate the Archive Support Module version
    In the ESET product's About or Help section, look for a component version labeled 'Archive Support Module', 'Archive Support', or similar. On Windows, this may also appear in the main log files or in Help > Support Tools. On Linux, check the ESET software documentation for the specific command to display module versions.
    Affected if The Archive Support Module version is visible in the product information.
  3. Compare module version to affected ranges
    Take the Archive Support Module version number found and compare it against version 1294. For most products, versions below 1294 are affected (e.g., 1293, 1292, etc.). For Eset Mobile Security, both versions below 1294 AND version 1294 itself are affected according to the advisory.
    Affected if The Archive Support Module version is lower than 1294, OR for Mobile Security specifically, the version is 1294 or lower.
  4. Verify RAR archive scanning is enabled
    Check the ESET product settings to confirm that scanning of compressed archives (RAR files) is enabled. On Windows, go to Setup > Computer Protection > Antivirus and antispyware > Archive scanning. Ensure RAR or 'All archives' scanning is not disabled or excluded.
    Affected if RAR archive scanning is enabled in the ESET configuration, making the bypass applicable.

If an ESET product is installed with an Archive Support Module version below 1294 (or 1294 or below for Mobile Security) and RAR archive scanning is enabled, the environment is affected by this vulnerability.

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.

From vendor data
Upgrade available Upgrade to 4 / 1294 or later
Fixed in 41294
Interim mitigation

Update all affected ESET products (Smart Security Premium, Internet Security, NOD32 Antivirus, Cyber Security Pro, Cyber Security, Mobile Security for Android, Smart TV Security, and NOD32 Antivirus 4 for Linux Desktop) to version 1294 or later of the Archive Support Module.

Fix this in Nod32 Antivirus Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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