16 matches found
xss-bypass-tester
No d...
EUVD-2018-18080
Malware in sbrugna...
EUVD-2018-18079
Malware in sbrugna...
SUSE-SU-2023:0167-1 Security update for bluez
This update for bluez fixes the following issues: - CVE-2022-3563: Fixed a potential crash in the mgmt-tester tool bsc1204426...
Sophos Tester Tool Denial of Service Vulnerability
Sophos Tester Tool is a penetration testing tool from Sophos UK. A security vulnerability exists in Sophos Tester Tool version 3.2.0.7 Beta, which stems from the program's failure to detect parameters of the DeviceIoControl code. An attacker can exploit the vulnerability to cause a blue screen or...
Sophos Tester Tool Arbitrary Code Execution Vulnerability
Sophos Tester Tool is a penetration testing tool from Sophos UK. A security vulnerability exists in Sophos Tester Tool version 3.2.0.7 Beta, which originates from the program's failure to detect DLLs, and can be exploited by an attacker to cause a denial of service and execute malicious code...
CVE-2018-6318
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.. ...
CVE-2018-6319
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 ...
Null pointer dereference
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 ...
CVE-2018-6318
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.. ...
CVE-2018-6319
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 ...
Input validation
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.. ...
CVE-2018-6319
The CVE affects Sophos Tester Tool 3.2.0.7 Beta: a driver accepts a special DeviceIoControl code and fails to validate the argument (a memory address). Passing NULL or invalid addresses can cause a Blue Screen of Death and, if triggered at boot, may result in a persistent denial of service. No re...
CVE-2018-6319
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 ...
CVE-2018-6318
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.. ...
CVE-2018-6318
The CVE-2018-6318 entry applies to Sophos Tester Tool 3.2.0.7 Beta. The vulnerability is a DLL hijacking flaw where the driver loads a DLL from userland (NTDLL.DLL) without validating the DLL’s signature or hash. An attacker could replace the DLL with a malicious one (locally or via remote access...