CVE-2018-6474
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 0x9C402148.
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 confidenceThe SASKUTIL.SYS driver in SUPERAntiSpyware Professional Trial 6.0.1254 does not validate input values from IOCTL code 0x9C402148, allowing local authenticated users to send specially crafted requests to the driver that trigger a kernel panic (BSOD) or potentially achieve unspecified privilege escalation or code execution in kernel context.
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.
-
Verify if SUPERAntiSpyware Professional is installedCheck for SUPERAntiSpyware in installed programs list via Control Panel > Programs and Features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object {$_.DisplayName -like "*SuperAntiSpyware*"}' in PowerShellAffected if SUPERAntiSpyware Professional Trial is listed as installed
-
Check the installed version of SUPERAntiSpywareRun the installed application and check About/Help > About, or query the version from the installation directory if known, or check the file version of saskutil.sys in the installation folderAffected if Version equals 6.0.1254 exactly (this specific version is vulnerable)
-
Verify the SASKUTIL.SYS driver is presentCheck for saskutil.sys in the SUPERAntiSpyware installation directory (typically C:\Program Files\SUPERAntiSpyware\ or C:\Program Files (x86)\SUPERAntiSpyware\) or check for loaded kernel drivers with 'driverquery /v | findstr saskutil'Affected if saskutil.sys file exists or the driver is loaded in memory
-
Confirm the driver is accessible for IOCTL interactionThis requires examining if the driver is running and accessible; on a live system with administrative privileges, you could use 'sc query saskutil' to check the driver service status, or use tools like WinObj to verify driver device object existence under \Device\Affected if The saskutil driver service is running or the device object is present and accessible
A user is affected if SUPERAntiSpyware Professional Trial version 6.0.1254 is installed with the saskutil.sys driver present and accessible, allowing a local authenticated attacker to send IOCTL code 0x9C402148 with malicious input to trigger a kernel panic or execute code in kernel context.
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 dataApply vendor patch if available; otherwise, uninstall SUPERAntiSpyware Professional Trial or remove/disable the vulnerable SASKUTIL.SYS driver until a patched version is released.
- Consultation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-6474 — 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-6474 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