CVE-2017-17049
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 0x82730010 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 confidenceTG Soft Vir.IT eXplorer Lite 8.5.42 contains a local privilege escalation/DoS vulnerability in the Viragtlt driver (\\.\Viragtlt). The vulnerability allows local users to trigger a NULL pointer dereference via a specially crafted DeviceIoControl request using control code 0x82730010 with a NULL value parameter, potentially leading to denial of service or unspecified other 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= 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.
-
Verify Vir.IT eXplorer Lite installationCheck for the presence of TG Soft Vir.IT eXplorer Lite in the system. Look in typical installation paths such as C:\Program Files\TG Soft or C:\Program Files (x86)\TG Soft, or query the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry named Vir.IT eXplorer Lite.Affected if The software is found installed on the system
-
Identify installed version numberLocate the executable (typically virit.exe or similar) in the installation directory, right-click and select Properties, then view the Details tab to read the File Version. Alternatively, check Add/Remove Programs or Programs and Features for the installed version.Affected if The installed version is exactly 8.5.42
-
Locate the vulnerable driver fileSearch for the driver file Viragtlt.sys within the Vir.IT installation directory. The driver is typically located in a subfolder such as driver or sys inside the main installation path.Affected if The file Viragtlt.sys exists in the installation directory
-
Check if driver is loadedOpen Command Prompt and run 'sc query Viragtlt' or use 'driverquery /v | findstr Viragtlt' to query the Windows driver database and determine if the driver service is currently loaded.Affected if The Viragtlt driver service is present and running
A system is affected if Vir.IT eXplorer Lite version 8.5.42 is installed with the Viragtlt driver present and loaded on the system.
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-supplied patch or upgrade to a patched version of Vir.IT eXplorer Lite. If no patch is available, restrict local user access to the system or implement application whitelisting to limit execution of code that could interact with the vulnerable driver.
- Consultation4.0 h
- Implementation4.0 h
- Testing3.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 $3,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-17049 — 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-17049 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