# CVE-2017-17049: Null dereference in n/a

> Local attackers can cause a denial of service in TG Soft Vir.IT eXplorer Lite via a crafted DeviceIoControl request.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Nov 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-4f59-x6gm-7h9h

## What is CVE-2017-17049?

CVE-2017-17049 is a high-severity vulnerability in n/a, published on 29 Nov 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

TG 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.

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2017-17049?

It affects 1 product.


Products: Tgsoft Vir.it Explorer.

## How do I fix CVE-2017-17049?

No fix has been published for CVE-2017-17049 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-17049 being exploited?

There is no known exploitation of CVE-2017-17049 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2017-17798](https://insights.sbomify.com/CVE-2017-17798/): Denial of service in n/a (high 7.8)
- [CVE-2017-17799](https://insights.sbomify.com/CVE-2017-17799/): Denial of service in n/a (high 7.8)
- [CVE-2017-17800](https://insights.sbomify.com/CVE-2017-17800/): Denial of service in n/a (high 7.8)
- [CVE-2017-17801](https://insights.sbomify.com/CVE-2017-17801/): Denial of service in n/a (high 7.8)
- [CVE-2017-17802](https://insights.sbomify.com/CVE-2017-17802/): Denial of service in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-17049 and fix it if it is affected.

What it is: CVE-2017-17049 is a high-severity vulnerability in n/a, published on 29 Nov 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-17049 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-17049/ (Markdown: https://insights.sbomify.com/CVE-2017-17049/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-17049
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-17049
- OSV: https://osv.dev/vulnerability/CVE-2017-17049

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-17049/
Summaries are generated and may contain mistakes; the official description above is the record.