dbcve.org
SuperantispywareApplication

CVE-2018-6476

CRITICAL · 9.8 CVSS v3.0 Published 2018-01-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
In SUPERAntiSpyware Professional Trial 6.0.1254, the SASKUTIL.SYS driver allows privilege escalation to NT AUTHORITY\SYSTEM because of not validating input values from IOCtl 0x9C402114 or 0x9C402124 or 0x9C40207c.

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 confidence

The SASKUTIL.SYS kernel driver in SUPERAntiSpyware Professional Trial 6.0.1254 fails to validate input values received through IOCTL codes 0x9C402114, 0x9C402124, and 0x9C40207c, enabling a local attacker to escalate privileges to NT AUTHORITY\SYSTEM.

MitigationApply the vendor-supplied update/patch for SUPERAntiSpyware to a version where input validation is properly implemented in the SASKUTIL.SYS driver, or uninstall the affected software if no patch is available.

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
SuperantispywareApplication
Affected:= 6.0.1254

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if SUPERAntiSpyware is installed
    Open Programs and Features (appwiz.cpl) or check for the software in the installation directory (typically C:\Program Files\SUPERAntiSpyware or C:\Program Files (x86)\SUPERAntiSpyware)
    Affected if SUPERAntiSpyware is present on the system
  2. Determine installed version of SUPERAntiSpyware
    Open the SUPERAntiSpyware application, go to Help > About, or check the version in the program's entry in Programs and Features
    Affected if Version is 6.0.1254 exactly (the affected version)
  3. Check for presence of SASKUTIL.SYS driver
    Open Command Prompt and run: driverquery /v | findstr SASKUTIL, or check C:\Windows\System32\drivers\SASKUTIL.SYS
    Affected if The SASKUTIL.SYS driver file exists on the system
  4. Verify driver version if accessible
    Right-click SASKUTIL.SYS in System32\drivers, select Properties, and check the File Version tab, or use a tool like sigcheck or PowerShell Get-ItemProperty
    Affected if Driver file version matches the vulnerable driver version 6.0.1254

A user is affected if SUPERAntiSpyware version 6.0.1254 with the SASKUTIL.SYS driver is installed on their 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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied update/patch for SUPERAntiSpyware to a version where input validation is properly implemented in the SASKUTIL.SYS driver, or uninstall the affected software if no patch is available.

Recommended fix Moderate confidence

Latest stable SuperAntiSpyware Professional release (version > 6.0.1254)

  1. 1. Visit the official SuperAntiSpyware website to download the latest version of the software.
  2. 2. Uninstall the current version of SuperAntiSpyware Professional Trial 6.0.1254.
  3. 3. Install the latest available version of SuperAntiSpyware from the official download source.
  4. 4. Verify the SASKUTIL.SYS driver version in the newly installed software matches a version after 6.0.1254.
  5. 5. Confirm the vulnerability is remediated by verifying the driver no longer accepts unvalidated input from IOCTL codes 0x9C402114, 0x9C402124, or 0x9C40207c.
Caveat Minor - standard software update; ensure compatibility with your existing security software stack

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Superantispyware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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