CVE-2017-10674
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 · uneditedAntiy Antivirus Engine 5.0.0.06281654 allows local users to cause a denial of service (BSOD) via a long third argument in a DeviceIoControl call.
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 confidenceAntiy Antivirus Engine 5.0.0.06281654 contains a kernel-mode driver with an input validation vulnerability in its DeviceIoControl handler. The driver fails to properly validate the length of the third argument (input buffer) before processing, allowing local users to trigger a buffer overflow that causes a Blue Screen of Death (BSOD). This is a local denial-of-service vulnerability requiring only low privileges.
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= 5.0.0.06281654CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Antiy Antivirus Engine is installedCheck for Antiy Antivirus in installed programs via Registry (HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall) or use 'wmic product' command to list installed softwareAffected if Antiy Antivirus Engine appears in installed programs listing
-
Confirm exact version of Antiy Antivirus EngineLocate the Antiy Antivirus installation directory (commonly in Program Files) and check the version information of the main executable, or run 'wmic product where "name like '%Antiy%'" get version,installlocation'Affected if Version reported equals 5.0.0.06281654 exactly
-
Identify Antiy kernel-mode driverSearch C:\Windows\System32\drivers\ for Antiy-related driver files (.sys) and check their version properties, or use 'driverquery /v | findstr -i antily' to list loaded Antiy driversAffected if An Antiy kernel driver is present and its version matches 5.0.0.06281654
-
Verify driver is currently loadedRun 'sc query type= driver' or use 'driverquery /v' to check if the Antiy driver is actively loaded in memoryAffected if An Antiy kernel driver shows as RUNNING in the service control manager
Environment is affected if Antiy Antivirus Engine version 5.0.0.06281654 is installed and its vulnerable kernel driver is loaded and active.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate to a patched version of Antiy Antivirus Engine. If no update is available, consider replacing the antivirus solution or restricting local access to prevent untrusted users from interacting with the vulnerable driver.
- Consultation4.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,288.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-10674 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-10674 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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