{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-6319 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-6319 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-6319 is a medium-severity vulnerability in n/a, published on 2 Feb 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-2018-6319 and fix it if it is affected.\n\nWhat it is: CVE-2018-6319 is a medium-severity vulnerability in n/a, published on 2 Feb 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-2018-6319 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-2018-6319/ (Markdown: https://insights.sbomify.com/CVE-2018-6319/index.md)","id":"CVE-2018-6319","markdown":"https://insights.sbomify.com/CVE-2018-6319/index.md","name":"CVE-2018-6319","record":{"aliases":["GHSA-x4pf-c598-7qg2"],"analysis":{"component_type":"operating_system","fix_type":"no_fix_stated","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Sophos Tester Tool","requires_auth":"low_privilege","summary":"A local attacker can cause a persistent Blue Screen of Death by passing invalid memory addresses to the Sophos Tester Tool driver.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"sophos_tester","vendor":"sophos"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.0"},"cwes":[{"id":"CWE-476","name":"NULL Pointer Dereference"}],"description":"In Sophos Tester Tool 3.2.0.7 Beta, the driver accepts a special DeviceIoControl code that doesn't check its argument. This argument is a memory address: if a caller passes a NULL pointer or a random invalid address, the driver will cause a Blue Screen of Death. If a program or malware does this at boot time, it can cause a persistent denial of service on the machine.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Null dereference in n/a","id":"CVE-2018-6319","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Other in n/a","id":"CVE-2018-6320"},"packages":[],"prev":{"headline":"Other in n/a","id":"CVE-2018-6318"},"products":["n/a"],"published":"2018-02-02","related":[{"cvss_score":7.8,"headline":"Other in n/a","id":"CVE-2018-6318","kev_date_added":null,"published":"2018-02-02"}],"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)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"A local attacker can cause a persistent Blue Screen of Death by passing invalid memory addresses to the Sophos Tester Tool driver.","url":"https://insights.sbomify.com/CVE-2018-6319/"}