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.
References
Link | Resource |
---|---|
https://29wspy.ru/exploits/CVE-2018-6318.pdf | Third Party Advisory |
https://29wspy.ru/exploits/CVE-2018-6318.pdf | Third Party Advisory |
Configurations
History
21 Nov 2024, 04:10
Type | Values Removed | Values Added |
---|---|---|
References | () https://29wspy.ru/exploits/CVE-2018-6318.pdf - Third Party Advisory |
Information
Published : 2018-02-02 21:29
Updated : 2024-11-21 04:10
NVD link : CVE-2018-6318
Mitre link : CVE-2018-6318
CVE.ORG link : CVE-2018-6318
JSON object : View
Products Affected
sophos
- sophos_tester
CWE
CWE-426
Untrusted Search Path