7 ms·

Slightly offtopic, but are vulns related to overflows no longer pocced publicly or are there mitigating factors which make exploitation impossible (eg K/ASLR et

Slightly offtopic, but are vulns related to overflows no longer pocced publicly or are there mitigating factors which make exploitation impossible (eg K/ASLR etc)? The specific CVE listings I'm referring to are: https://www.cvedetails.com/vulnerability-list/vendor_id-5842/product_id-9978/Videolan-Vlc-Media-Player.html https://www.cvedetails.com/vulnerability-list/vendor_id-5842... https://www.cvedetails.com/vulnerability-list/vendor_id-26/product_id-32238/Microsoft-Windows-10.html https://www.cvedetails.com/vulnerability-list/vendor_id-26/p...

wepple 7y ago
Building a PoC to prove you can get reliable code execution is typically 10x harder than finding an issue and patching it. The modern approach is to assume that most types of memory corruption could be exploitable, and just patch. Especially given that an inability for one person to reliably PoC does not mean it’s not exploitable; as soon as you say it’s not exploitable, Mark Dowd shows up and exploits the bug.