CVE-2017-18019: Input Validation
First published: Thu Jan 04 2018(Updated: )
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.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| K7 Computing Total Security | <15.1.0.305 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2017-18019?
CVE-2017-18019 has a medium severity rating due to its potential for unauthorized memory access.
How do I fix CVE-2017-18019?
To fix CVE-2017-18019, update K7 Total Security to version 15.1.0.305 or later.
What software is affected by CVE-2017-18019?
CVE-2017-18019 affects K7 Total Security versions prior to 15.1.0.305.
What type of vulnerability is CVE-2017-18019?
CVE-2017-18019 is a memory access vulnerability caused by insufficient input sanitization.
Can CVE-2017-18019 lead to data breaches?
Yes, CVE-2017-18019 could potentially allow attackers to read sensitive information from memory.
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/references
- agent/severity
- agent/author
- agent/last-modified-date
- agent/weakness
- agent/description
- agent/first-publish-date
- agent/softwarecombine
- agent/event
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/k7computing
- canonical/k7 computing total security