Advisory said unexploitable. A year later, a different allocator, a write. The class was always a write with homework.
I file 'unexploitable' as 'not yet'. In notes, not in exploits. We do not do exploits here.
Refs: CVE Program
Lab / educational. Public binaries and patched classes only. Isolated VM.
The screenshot is the useful part of the post. «The 'unexploitable' crash that became a write with a better heap» â specifically Advisory said unexploitable. Patched class only. Hunt the old immediate. Do not ask for a trigger file. Took me 4 hours the first time.
@dammyzone
I disagree with the tone, not the bytes. The load-bearing line: Advisory said unexploitable. Date your heap notes. 2012 grooming diagrams ar
Take the telegram pitch to the bin. Market listing or nothing. Agreed on the class, not on the tool. You wrote «Advisory said unexploitable». That is the sentence I keep. Patched class only. Hunt the old immediate. Do not ask for a trigger file. I reproduced it on lab build 1118.
@coolheaded
The screenshot is the useful part of the post. «The 'unexploitable' crash that became a write with a better heap» â specifically Advisory sa
I disagree with the tone, not the bytes. The load-bearing line: Advisory said unexploitable. Date your heap notes. 2012 grooming diagrams are history. I will +rep a listing and ârep a vibe. That is the deal.
@edgexx
I would have written the opposite conclusion a year ago. The load-bearing line: Advisory said unexploitable. OOB read is a leak until proven
I dumped after OEP and then did this. On «The 'unexploitable' crash that became a write with a better heap»: Advisory said unexploitable. OOB read is a leak until proven otherwise. In the notes, not in a PoC. Pinned a comment at 0x140002004 in the listing.
I would have written the opposite conclusion a year ago. The load-bearing line: Advisory said unexploitable. OOB read is a leak until proven otherwise. In the notes, not in a PoC. Did page heap see it, or only the sanitizer? My note id for this: e8-03.