CVE-2018-6472
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 · uneditedIn SUPERAntiSpyware Professional Trial 6.0.1254, the driver file (SASKUTIL.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 0x9C40204c.
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 confidenceThe SASKUTIL.SYS driver in SUPERAntiSpyware Professional Trial 6.0.1254 fails to validate input values received from IOCTL 0x9C40204c. This input validation flaw allows local, unprivileged users to send specially crafted requests to the kernel-mode driver, potentially triggering a system crash (Blue Screen of Death) or achieving unspecified further impact.
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= 6.0.1254CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm SUPERAntiSpyware installation and versionOpen the application and check About/Version information, or look in Add/Remove Programs for the installed version numberAffected if The installed version is 6.0.1254 (the only affected version listed)
-
Locate the SASKUTIL.SYS driver fileSearch for SASKUTIL.SYS in the SUPERAntiSpyware installation directory (typically C:\Program Files\SUPERAntiSpyware\ or C:\Program Files (x86)\SUPERAntiSpyware\)Affected if The SASKUTIL.SYS file exists in the installation directory and matches version 6.0.1254
-
Check if SASKUTIL.SYS driver is loadedOpen an elevated command prompt and run 'sc query saskutil' or 'driverquery /v | findstr saskutil' to query driver statusAffected if The saskutil service is running and the driver is loaded into kernel memory
-
Verify driver file versionRight-click SASKUTIL.SYS, select Properties, then view the Details tab for file version informationAffected if The file version shows 6.0.1254.XXXX (where XXXX varies) confirming the vulnerable driver version
A user is affected if SUPERAntiSpyware Professional Trial version 6.0.1254 is installed and the SASKUTIL.SYS driver is loaded, exposing the unpatched input validation vulnerability in IOCTL 0x9C40204c.
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 dataRemove SUPERAntiSpyware Professional Trial if no longer needed, or restrict access to the driver to prevent unprivileged local users from communicating with it. If the software is still required, contact the vendor for an updated version that addresses the input validation vulnerability.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-6472 — 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-2018-6472 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