dbcve.org
Zillya\! AntivirusApplication · Zillya

CVE-2018-5958

HIGH · 7.8 CVSS v3.0 Published 2018-01-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
In Zillya! Antivirus 3.0.2230.0, the driver file (zef.sys) allows local users to cause a denial of service (BSOD) or possibly have unspecified other impact because of not validating input values from IOCtl 0x9C402424.

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 zef.sys kernel driver in Zillya! Antivirus fails to validate input parameters received through IOCTL code 0x9C402424, allowing local unprivileged users to send specially crafted requests that trigger a kernel panic (BSOD) or potentially achieve code execution with kernel privileges.

MitigationDeploy the vendor-supplied patch for this vulnerability, or if unavailable, restrict local user access to the antivirus driver and consider alternative security solutions. Network segmentation can limit the local attack surface.

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
Zillya\! AntivirusApplication
Affected:= 3.0.2230.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
High
Integrity
High
Availability
High

CVSS:3.0/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. Verify Zillya! Antivirus is installed
    Check the system for Zillya! Antivirus by examining installed programs in the registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall or using 'Get-WmiObject -Class Win32_Product' in PowerShell
    Affected if Zillya! Antivirus appears in the list of installed software
  2. Check Zillya! Antivirus version
    Locate the Zillya! Antivirus installation directory (typically C:\Program Files\Zillya! Antivirus or C:\Program Files (x86)\Zillya! Antivirus) and check the version of the main executable, or query the version via registry key if available
    Affected if The installed version is exactly 3.0.2230.0
  3. Verify zef.sys driver presence
    Check for the presence of zef.sys in the Windows\System32\drivers directory or enumerate loaded drivers using 'driverquery /v' or 'Get-ProcessModule' in PowerShell to look for zef.sys
    Affected if The zef.sys driver file exists on the system or appears in the list of loaded kernel drivers
  4. Test driver accessibility via IOCTL
    Use a driver communication tool such as OSR Driver Loader or write a small program to send IOCTL code 0x9C402424 to the zef.sys driver via DeviceIoControl API (device name typically \\Device\Zillya or similar)
    Affected if The driver accepts the IOCTL request without error, indicating the vulnerable code path is present and accessible

A system is affected if Zillya! Antivirus version 3.0.2230.0 is installed with the zef.sys driver present and accessible via IOCTL 0x9C402424, allowing local unprivileged users to trigger kernel-level code execution.

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

Deploy the vendor-supplied patch for this vulnerability, or if unavailable, restrict local user access to the antivirus driver and consider alternative security solutions. Network segmentation can limit the local attack surface.

Fix this in Zillya\! Antivirus Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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