dbcve.org
Nprotect AvsApplication · Inca

CVE-2018-6522

HIGH · 7.8 CVSS v3.0 Published 2018-02-02
Fix available
A fix is available. Upgrade to 4.0.0.39 or later.
See remediation →
80/100
Remediation priority · High
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 nProtect AVS V4.0 before 4.0.0.39, the driver file (TKRgFtXp.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 0x220408.

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 nProtect AVS V4.0 kernel driver (TKRgFtXp.SYS) fails to validate input values when processing IOCTL code 0x220408, allowing local unprivileged users to trigger a kernel-mode crash (BSOD) and potentially achieve arbitrary code execution in kernel context.

MitigationApply vendor patch to update nProtect AVS to version 4.0.0.39 or later, which contains proper input validation in the driver.

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
Nprotect AvsApplication
Affected:>= 4.0, < 4.0.0.39

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
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 checks

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

  1. Verify nProtect AVS installation
    Check installed programs list in Windows Control Panel > Programs and Features, or run: Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -like '*nProtect*'}
    Affected if nProtect AVS appears in the installed programs list
  2. Identify installed nProtect AVS version
    Check the program's version property from the installation above, or look in the program directory for version information
    Affected if Installed version is 4.0.x where x is less than 39 (versions 4.0.0.0 through 4.0.0.38)
  3. Locate the kernel driver file TKRgFtXp.SYS
    Search for TKRgFtXp.SYS in the nProtect installation directory, typically found in C:\Program Files\nProtect or C:\Program Files (x86)\nProtect
    Affected if The driver file TKRgFtXp.SYS exists in the nProtect installation folder
  4. Confirm driver is loaded in kernel
    Run 'sc query TKRgFtXp' or check the Windows driver list via 'driverquery /v | findstr TKRgFtXp' to see if the driver is actively loaded
    Affected if Driver shows as RUNNING or STARTED in the service status

If nProtect AVS version is 4.0.0.38 or earlier and the TKRgFtXp.SYS driver is loaded in kernel mode, the system is vulnerable to the IOCTL 0x220408 buffer handling flaw.

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
Upgrade available Upgrade to 4.0.0.39 or later
Fixed in 4.0.0.39
Interim mitigation

Apply vendor patch to update nProtect AVS to version 4.0.0.39 or later, which contains proper input validation in the driver.

Fix this in Nprotect Avs Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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