{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-6318 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-6318 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-6318 is a high-severity vulnerability in n/a, published on 2 Feb 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2018-6318 and fix it if it is affected.\n\nWhat it is: CVE-2018-6318 is a high-severity vulnerability in n/a, published on 2 Feb 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2018-6318 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-6318/ (Markdown: https://insights.sbomify.com/CVE-2018-6318/index.md)","id":"CVE-2018-6318","markdown":"https://insights.sbomify.com/CVE-2018-6318/index.md","name":"CVE-2018-6318","record":{"aliases":["GHSA-9c2c-8x33-xrjv"],"analysis":{"component_type":"desktop_application","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Sophos Tester Tool","requires_auth":"none","summary":"Attackers can execute arbitrary code via DLL hijacking in Sophos Tester Tool due to lack of DLL validation during loading.","user_interaction":"required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"sophos_tester","vendor":"sophos"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-426","name":"Untrusted Search Path"}],"description":"In Sophos Tester Tool 3.2.0.7 Beta, the driver loads (in the context of the application used to test an exploit or ransomware) the DLL using a payload that runs from NTDLL.DLL (so, it's run in userland), but the driver doesn't perform any validation of this DLL (not its signature, not its hash, etc.). A person can change this DLL in a local way, or with a remote connection, to a malicious DLL with the same name -- and when the product is used, this malicious DLL will be loaded, aka a DLL Hijacking attack.","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":"Other in n/a","id":"CVE-2018-6318","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Null dereference in n/a","id":"CVE-2018-6319"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2018-6317"},"products":["n/a"],"published":"2018-02-02","related":[{"cvss_score":5.5,"headline":"Null dereference in n/a","id":"CVE-2018-6319","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":"Attackers can execute arbitrary code via DLL hijacking in Sophos Tester Tool due to lack of DLL validation during loading.","url":"https://insights.sbomify.com/CVE-2018-6318/"}