dbcve.org
Twister AntivirusApplication · Filseclab

CVE-2024-1140

MEDIUM · 6.1 CVSS v3.1 Published 2024-02-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
63/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
Twister Antivirus v8.17 is vulnerable to an Out-of-bounds Read vulnerability by triggering the 0x801120B8 IOCTL code of the filmfd.sys driver.

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

Twister Antivirus v8.17 contains an out-of-bounds read vulnerability in the filmfd.sys kernel-mode driver when handling IOCTL code 0x801120B8. This memory safety issue allows reading beyond allocated buffer boundaries, potentially leaking sensitive kernel memory contents to user-mode callers.

MitigationUpdate to a patched version of Twister Antivirus that addresses the vulnerability in filmfd.sys, or contact the vendor for a hotfix. As a kernel driver issue, workarounds are limited; disabling the antivirus product may reduce protection but eliminates the 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
Twister AntivirusApplication
Affected:= 8.17

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/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. Confirm Twister Antivirus is installed and identify its version
    Check the installed version via the Windows Registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Twister Antivirus or by locating the program in Control Panel Programs and Features. Alternatively, right-click the Twister Antivirus tray icon and select 'About' to view version information.
    Affected if The installed version is exactly 8.17. Any other version is not affected by this specific CVE.
  2. Locate the filmfd.sys driver on the system
    Search for filmfd.sys in the Windows system directories: typically C:\Windows\System32\drivers\ and C:\Program Files\Filseclab\Twister Antivirus\. Use Windows Explorer search or run 'dir /s C:\filmfd.sys' from an elevated command prompt.
    Affected if The file filmfd.sys exists on the system. Its presence indicates the vulnerable driver component is installed.
  3. Verify the driver is currently loaded in kernel memory
    Open an elevated command prompt and run 'sc query filmfd' or 'driverquery /v | findstr filmfd' to check if the driver service is active. Also check Device Manager for the driver under 'Non-Plug and Play Drivers' if visible.
    Affected if The driver shows as RUNNING or STARTED in the service status, meaning the vulnerable IOCTL handler is active and accessible.
  4. Identify if the specific vulnerable IOCTL 0x801120B8 is exposed
    This requires either analyzing the driver binary for the IOCTL handler code or using a tool to send the specific IOCTL request to the driver. Without a specialized tool or driver analysis, this is not directly verifiable through standard Windows utilities.
    Affected if A tool or script successfully sends IOCTL 0x801120B8 and receives data beyond expected buffer boundaries, indicating the vulnerable code path is reachable.

You are affected if Twister Antivirus version 8.17 is installed AND the filmfd.sys driver is present and loaded on the system, exposing the vulnerable IOCTL handler.

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

Update to a patched version of Twister Antivirus that addresses the vulnerability in filmfd.sys, or contact the vendor for a hotfix. As a kernel driver issue, workarounds are limited; disabling the antivirus product may reduce protection but eliminates the attack surface.

Fix this in Twister Antivirus Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing10.0 h
  • Review / QA6.0 h
28.0 hours of engineering $4,820
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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