dbcve.org
Escan Internet Security SuiteApplication · Escanav

CVE-2018-10098

MEDIUM · 5.5 CVSS v3.0 Published 2018-07-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/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
In MicroWorld eScan Internet Security Suite (ISS) for Business 14.0.1400.2029, the driver econceal.sys allows a non-privileged user to send a 0x830020E0 IOCTL request to \\.\econceal to cause a denial of service (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

The econceal.sys kernel-mode driver in MicroWorld eScan Internet Security Suite 14.0.1400.2029 does not properly handle a specific IOCTL request (0x830020E0). A non-privileged local user can send this IOCTL to the device interface \\.\\econceal, causing the driver to trigger a kernel panic resulting in a Blue Screen of Death (BSOD), achieving denial of service.

MitigationApply vendor-provided patches or updates to eScan ISS that address the vulnerable econceal.sys driver. If no patch is available, contact MicroWorld for remediation guidance or consider disabling/removing the affected component until a fix is released.

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
Escan Internet Security SuiteApplication
Affected:= 14.0.1400.2029

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

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/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. Check if eScan Internet Security Suite is installed
    Open Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ or look for 'eScan' in Add/Remove Programs. Alternatively, check C:\Program Files\eScan or C:\Program Files (x86)\eScan for installation directories.
    Affected if eScan Internet Security Suite is found installed on the system
  2. Locate the econceal.sys driver file
    Search for econceal.sys in the eScan installation directory, typically under C:\Program Files\eScan\ or C:\Windows\System32\drivers\. Use the command: dir /s C:\econceal.sys or Get-ChildItem -Path C:\ -Filter econceal.sys -Recurse -ErrorAction SilentlyContinue
    Affected if The file econceal.sys exists on the system
  3. Verify the driver file version
    Right-click econceal.sys, select Properties, then view the Details tab for Product Version and File Version. Alternatively, use PowerShell: (Get-Item 'C:\Program Files\eScan\econceal.sys').VersionInfo or use sigverif.exe
    Affected if The driver version equals 14.0.1400.2029 or matches the vulnerable product version
  4. Confirm the vulnerable device interface exists
    Open Command Prompt and run: reg query 'HKLM\SYSTEM\CurrentControlSet\Services\econceal' to check if the driver service is registered. Then verify device presence using: wmic sysdriver get name,pathname where name like '%econceal%'
    Affected if The econceal service is registered and the driver is loaded or loadable
  5. Identify the product version via registry
    Run: reg query 'HKLM\SOFTWARE\MicroWorld\eScan' /v Version or check HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{GUID} for DisplayVersion
    Affected if The installed product version matches 14.0.1400.2029 exactly

The system is affected if eScan Internet Security Suite version 14.0.1400.2029 is installed with the econceal.sys driver present, as this specific version and driver combination is vulnerable to the IOCTL 0x830020E0 denial-of-service flaw.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-provided patches or updates to eScan ISS that address the vulnerable econceal.sys driver. If no patch is available, contact MicroWorld for remediation guidance or consider disabling/removing the affected component until a fix is released.

Fix this in Escan Internet Security Suite Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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