{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-18019 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-18019 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-18019 is a high-severity vulnerability in n/a, published on 4 Jan 2018. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-18019 and fix it if it is affected.\n\nWhat it is: CVE-2017-18019 is a high-severity vulnerability in n/a, published on 4 Jan 2018. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-18019 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2017-18019/ (Markdown: https://insights.sbomify.com/CVE-2017-18019/index.md)","id":"CVE-2017-18019","markdown":"https://insights.sbomify.com/CVE-2017-18019/index.md","name":"CVE-2017-18019","record":{"aliases":["GHSA-6xcc-8jcr-hfj7"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["data_read","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"K7 Total Security","requires_auth":"low_privilege","summary":"An attacker can read arbitrary memory or cause a crash via unsanitized input to the K7Sentry device in K7 Total Security.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"total_security","vendor":"k7computing"}],"cvss":{"score":7.1,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H","version":"3.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"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.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2017-10-23","github_poc":1,"max_poc_stars":1,"metasploit":0,"nuclei":0,"refs":[{"date":"2023-12-01T23:59:07Z","kind":"github_poc","ref":"https://github.com/SpiralBL0CK/CVE-2017-18019","stars":1,"title":"Under Construction :) Please come back later"},{"date":"2017-10-23","kind":"exploitdb","ref":"44046","stars":null,"title":"K7 Total Security 15.1.0.305 - Device Driver Arbitrary Memory Read"}],"tier":"poc_unverified"},"has_fix":null,"headline":"Information disclosure in n/a","id":"CVE-2017-18019","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2017"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in n/a","id":"CVE-2017-18020"},"packages":[],"prev":{"headline":"Race condition in n/a","id":"CVE-2017-18018"},"products":["n/a"],"published":"2018-01-04","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"An attacker can read arbitrary memory or cause a crash via unsanitized input to the K7Sentry device in K7 Total Security.","url":"https://insights.sbomify.com/CVE-2017-18019/"}