dbcve.org
Twister AntivirusApplication · Filseclab

CVE-2023-0907

MEDIUM · 5.5 CVSS v3.1 Published 2023-02-18
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
A vulnerability, which was classified as problematic, has been found in Filseclab Twister Antivirus 8.17. Affected by this issue is the function 0x220017 in the library ffsmon.sys of the component IoControlCode Handler. The manipulation leads to denial of service. An attack has to be approached locally. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-221456.

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

A denial of service vulnerability exists in the ffsmon.sys kernel driver of Filseclab Twister Antivirus 8.17. The vulnerability is in the IoControlCode handler function 0x220017, which can be exploited locally to cause a denial of service condition. A public exploit exists for this vulnerability.

MitigationUpdate Filseclab Twister Antivirus to the latest version to obtain patched drivers, or if no update is available, consider disabling or removing the affected ffsmon.sys driver if possible.

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

CVSS:3.1/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. Verify Twister Antivirus installation and version
    Check for Filseclab Twister Antivirus installation and confirm the version number. Common locations: Program Files\Filseclab\Twister Antivirus\ or check registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for the product entry.
    Affected if The installed version is exactly 8.17. Only version 8.17 is affected; other versions are not vulnerable to this CVE.
  2. Locate the ffsmon.sys driver file
    Search for ffsmon.sys in the Twister Antivirus installation directory (typically Program Files\Filseclab\Twister Antivirus\ or subfolders like drivers\ or system\). Also check C:\Windows\System32\drivers\.
    Affected if The ffsmon.sys file exists in the Twister Antivirus directory or drivers folder. This driver must be present for the vulnerability to be exploitable.
  3. Check if ffsmon.sys driver is loaded
    Open an elevated command prompt and run: sc query ffsmon or check Device Manager for hidden/system devices. Also check driver signature status using sigcheck or verify the driver is listed in registry under HKLM\SYSTEM\CurrentControlSet\Services.
    Affected if The ffsmon.sys driver is actively loaded or present in the system services. The vulnerability requires the driver to be loaded to accept malicious IOCTL requests.
  4. Verify IOCTL handler 0x220017 is accessible
    This check requires analyzing the driver or monitoring IOCTL calls. Use tools like WinObj or Process Monitor to observe communication with the driver device (typically named \\Device\ffsmon or similar). The specific IOCTL code 0x220017 must be reachable.
    Affected if The driver is exposed and accepting IOCTL communications. If the driver is disabled or blocked from accepting IOCTL requests, the attack surface is reduced.

You are affected if Filseclab Twister Antivirus version 8.17 is installed AND the ffsmon.sys kernel driver is present and loaded on the system.

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 Filseclab Twister Antivirus to the latest version to obtain patched drivers, or if no update is available, consider disabling or removing the affected ffsmon.sys driver if possible.

Fix this in Twister Antivirus Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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