CVE-2018-6318
First published: Fri Feb 02 2018(Updated: )
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.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Sophos Sophos Tester | =3.2.0.7-beta |
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-2018-6318?
CVE-2018-6318 has a medium severity rating due to its potential to allow unauthorized execution of code.
How do I fix CVE-2018-6318?
To mitigate CVE-2018-6318, update to a patched version of Sophos Tester Tool that addresses this vulnerability.
What systems are affected by CVE-2018-6318?
CVE-2018-6318 specifically affects Sophos Tester Tool version 3.2.0.7 Beta.
What types of attacks can CVE-2018-6318 facilitate?
CVE-2018-6318 can facilitate code execution attacks by exploiting the lack of DLL validation.
Is there a known exploit for CVE-2018-6318?
Yes, there are proofs of concept that show how CVE-2018-6318 can be exploited to execute arbitrary code.
- collector/nvd-index
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/weakness
- agent/severity
- agent/references
- agent/author
- agent/tags
- agent/description
- agent/first-publish-date
- agent/event
- agent/source
- vendor/sophos
- canonical/sophos sophos tester
- version/sophos sophos tester/3.2.0.7-beta