CVE-2023-1369
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 · uneditedA vulnerability was found in TG Soft Vir.IT eXplorer 9.4.86.0. It has been rated as problematic. This issue affects the function 0x82730088 in the library VIRAGTLT.sys of the component IoControlCode Handler. The manipulation leads to denial of service. The attack needs to be approached locally. The exploit has been disclosed to the public and may be used. Upgrading to version 9.5 is able to address this issue. It is recommended to upgrade the affected component. The associated identifier of this vulnerability is VDB-222875.
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 confidenceA denial of service vulnerability exists in TG Soft Vir.IT eXplorer antivirus driver (VIRAGTLT.sys) in the IoControlCode handler function 0x82730088. A local attacker can trigger this vulnerability to cause a denial of service condition. The exploit has been publicly disclosed.
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= 9.4.86.0= 1.86.0.0CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 is installedCheck for Vir.IT eXplorer installation by looking in Add/Remove Programs (Windows) or checking for the program directory, typically under C:\Program Files\TG Soft\ or C:\Program Files (x86)\TG Soft\Affected if Vir.IT eXplorer is found on the system
-
Check Vir.IT eXplorer application versionOpen Vir.IT eXplorer and navigate to Help > About, or check the version property of the executable file (usually named VirIT.exe) in the installation folderAffected if Version is 9.4.86.0 exactly
-
Locate and verify VIRAGTLT.sys driver versionFind the driver file VIRAGTLT.sys in the Windows System32\drivers folder or Vir.IT installation directory, then right-click the file, select Properties, and check the File Version on the Details tabAffected if Driver file version shows 1.86.0.0
-
Confirm driver is loadedOpen Command Prompt as Administrator and run: driverquery /v | findstr VIRAGTLT, or check Device Manager under Non-Plug and Play Drivers for Vir.IT Explorer driverAffected if Driver appears in the driver list and is in a running state
A system is affected if Vir.IT eXplorer version 9.4.86.0 or VIRAGTLT.sys driver version 1.86.0.0 is installed and the driver is 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.
dbcve · scopedUpgrade Vir.IT eXplorer to version 9.5 to address this vulnerability. As this is a local privilege escalation/DoS vulnerability in a kernel driver, limiting local access to affected systems provides additional risk reduction until the upgrade can be applied.
version 9.5
- Upgrade Vir.IT eXplorer from version 9.4.86.0 to version 9.5 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-1369 — 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-2023-1369 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