News for hackers. Stuff that matters.
Re:Open-Sourcing ClusterFuzz by daeken on Thursday February 07, 2019 @02:26PM (#19107703)
People drastically underestimate the prevalence and impact of UAF attacks. They're extremely common in complex applications and often lead to everything from information leaks to code execution. That's why almost every browser exploit (of the last ~10 years at least) uses at least one UAF in their chain.
Re:Open-Sourcing ClusterFuzz by saagarjha on Thursday February 07, 2019 @04:30PM (#19108777)
> That's why almost every browser exploit (of the last ~10 years at least) uses at least one UAF in their chain.

That's usually because the "low-hanging fruit" is mostly gone due to protections like stack canaries, CFI checks, address randomization, and sandboxing, which makes things like buffer overflows or jumping to shellcode more difficult.

Re:Open-Sourcing ClusterFuzz by pjmlp on Thursday February 07, 2019 @04:45PM (#19108892)
Yet the Linux Kernel Self Preservation project is still in a getting there kind of state.
Re:Open-Sourcing ClusterFuzz by saagarjha on Friday February 08, 2019 @01:18AM (#19111981)
Sorry, what?
Re:Open-Sourcing ClusterFuzz by pjmlp on Friday February 08, 2019 @01:48AM (#19112079)
That low hanging fruit is not gone on the Linux kernel, for more info check Linux Kernel Summit 2018 and Linux New Zealand Conference 2019.