CVE-2017-17050
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 · uneditedTG Soft Vir.IT eXplorer Lite 8.5.42 allows local users to cause a denial of service (NULL pointer dereference) or possibly have unspecified other impact via a NULL value in a 0x82730020 DeviceIoControl request to \\.\Viragtlt.
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 confidenceIn TG Soft Vir.IT eXplorer Lite 8.5.42, the Viragtlt device driver (\\.\Viragtlt) does not properly validate input when handling DeviceIoControl requests with code 0x82730020. When a local user sends a request containing a NULL value, the driver attempts to dereference the NULL pointer, causing a denial of service (crash). The 'possibly unspecified other impact' suggests potential for privilege escalation if the NULL pointer could be controlled to point to attacker-controlled memory.
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= 8.5.42CVSS 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.
-
Check if Viragtlt driver file existsSearch for Viragtlt.sys in C:\Windows\System32\drivers\ or use 'dir /s C:\Viragtlt.sys' to locate the driver file on the systemAffected if The Viragtlt.sys driver file is present on the system
-
Check Vir.IT eXplorer Lite installation versionCheck the installed version via Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ or check the program files directory for Vir.IT eXplorer LiteAffected if The installed version is exactly 8.5.42
-
Verify device driver is loadedOpen Command Prompt and run 'sc query Viragtlt' or check Device Manager for the Viragtlt driver under non-plug and play driversAffected if The Viragtlt service exists and is in a running or stopped state indicating the driver is registered
A system is affected if the Viragtlt driver (Viragtlt.sys) is present AND the installed Vir.IT eXplorer Lite version is exactly 8.5.42, as this specific version contains the driver with the NULL pointer dereference vulnerability in DeviceIoControl handler 0x82730020.
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 patches or update to a newer version of Vir.IT eXplorer Lite that properly validates input in the Viragtlt device driver before processing DeviceIoControl requests. Restrict local untrusted user access to the system as an interim compensating control.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-17050 — 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-17050 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