Sophos Tester 3.2.0.7 Beta

Submit a proposal Propose CVE/GCVE/GHSA reference

Approved changes feed: RSS · Atom

cpe:2.3:a:sophos:sophos_tester:3.2.0.7:beta:*:*:*:*:*:*

part: a version: 3.2.0.7 update: beta

VendorSophos (a481dca1-298d-56ee-9d5c-373f6e8cead2)
ProductSophos Tester (e1614071-41bc-5fc8-9779-dc15ad45cf3c)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*
NotesImported from NVD CPE 2.0 feed

PURL mappings

PURLSourceLast updated
No PURL mappings for this CPE yet.

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2018-6319 vulnerable 2026-06-03 14:39:00.126447 Details available
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.
Published: 2018-02-02T21:00:00.000Z
Updated: 2024-08-05T06:01:48.544Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2018-6318 vulnerable 2026-06-03 14:39:00.126048 Details available
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.
Published: 2018-02-02T21:00:00.000Z
Updated: 2024-08-05T06:01:48.911Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.