News for hackers. Stuff that matters.
Re:Virtually Unlimited Memory: Escaping the Chrome Sandbox by jcelerier on Tuesday April 16, 2019 @04:21AM (#19672001)
> This is yet another use-after-free in C++ code.

Use-after-free is the least common case of CVE in C++ : https://resources.whitesourcesoftware.com/research-reports/w...

Re:Virtually Unlimited Memory: Escaping the Chrome Sandbox by xyzzy123 on Tuesday April 16, 2019 @04:53AM (#19672137)
Hm, a few years ago when I was actively fuzzing stuff, UAFs were something like 20-30% of the crashes and one of the more exploitable memory corruption bug classes.

I will grant that the fuzzing targets were browsers, pdf readers, office suites and stuff which have some characteristics not shared by all C++ software.

In particular, a script engine and usually a way for “native” objects to get referenced or frobbed by scripting. Along with complex trees of object references, custom allocators, object pools etc.

I would have loved to have written a more substantive response but I didn’t want to download the PDF and check their analysis because they wanted to harvest my email.

What I can say is that a large proportion of real-world attacks where a hapless user gets pwned by a malicious file, document or script have a UAF somewhere down below as a root cause.

Not sure how UAF as a bug class got rated “least common” in their analysis? Would love to see some insight here, it doesn’t mesh at all with my lived experience but of course I could be missing something.

Re:Virtually Unlimited Memory: Escaping the Chrome Sandbox by jcelerier on Tuesday April 16, 2019 @05:33AM (#19672269)
> I would have loved to have written a more substantive response but I didn’t want to download the PDF and check their analysis because they wanted to harvest my email.

huh, they didn't ask me for any email (or maybe ublock handled it).

Re:Virtually Unlimited Memory: Escaping the Chrome Sandbox by xyzzy123 on Tuesday April 16, 2019 @07:27AM (#19672706)
Thanks, I should have tried harder, any old email will do.

After looking at the paper I think the issue is that they are counting CWEs assigned to CVEs, but CWE assignment to CVEs is not very granular / accurate.

For a contrasting point of view here’s an alternative reference:

“FreeSentry: Protecting Against Use-After-Free Vulnerabilities Due to Dangling Pointers” - https://pdfs.semanticscholar.org/3829/df26d4ce686251b9b50308... - “In 2011 and 2012, the most exploited memory errors for Microsoft products were use-after-free vulnerabilities. It was also the most exploited vulnerability for both Windows Vista and Windows 7 and is the most common type of memory error that occurs in Internet Explorer.”. Ok, that’s a bit old. Also why doesn’t it show up in the data?

In an unscientific sanity check (bit slow to do because on mobile) I am not sure UAF is getting all the credit it deserves in CVE classification.

For example https://www.cvedetails.com/cve-details.php?t=1&cve_id=CVE-20... is a UAF (https://www.exploit-db.com/exploits/46184) but is listed as CWE category 264 (permissions, privileges and access controls).

CVE-2017-8540 https://www.cvedetails.com/cve/cve-2017-8540 is also a UAF but is listed as CWE category 119 (memory corruption / code exec), ref: https://www.exploit-db.com/exploits/42088

I think I could find a lot more. CWE assignment to CVEs is not really an exact science. I suspect UAFs are getting under-counted because the bugs just went into “privesc” or “memory corruption / buffer overflow” buckets.

Re:Virtually Unlimited Memory: Escaping the Chrome Sandbox by patternmaster on Tuesday April 16, 2019 @12:25PM (#19674997)
Hey xyzzy123, are you available for some freelancing on the subject?