←
LiveOverflow 🔴 hextree.io10,592 posts
LiveOverflow 🔴 hextree.io avatar✓

LiveOverflow 🔴 hextree.io ✓

@LiveOverflow

wannabe hacker... he/him 🌱 grow your hacking skills @hextreeio

◷ Joined March 2015▧ 2,279 Photos and videos
LiveOverflow 🔴 hextree.io avatar
LiveOverflow 🔴 hextree.io@LiveOverflow·14h

Can any datacenter admins/builders weigh in on the prevalence of avx512f, avx512bw, avx512vbmi, and bmi2? All my servers or VMs don't have it

itszn avatar
⟳ LiveOverflow 🔴 hextree.io retweeted
itszn@itszn13·17h

We found that GPT-6.2 was another step up in vulnerability research akin to the leap we saw from 5.6 -> 6 On unseen v8 bugs: an increase of 22%! Along with this, our team worked hard to bring large improvements in secure code generation and secure and complete patch generation

Post attachmentPost attachmentPost attachmentPost attachment
Gynvael Coldwind avatar
⟳ LiveOverflow 🔴 hextree.io retweeted
Gynvael Coldwind@gynvael·Nov 15

I'm reading Marcus' recent post and I'm not exactly sure where is this coming from. A few things: 1. FFmpeg has a history of quickly fixing reported bugs, and before 2025 Google has reported literally thousands of security vulnerabilities to FFmpeg, which were fixed within days. Then FFmpeg switched to a new X/Twitter PR approach and suddenly reporting all discovered bugs somehow became bad? 2. FFmpeg is known to be broken. It doesn't matter if the bugs are disclosed after 90 days, 60 days, 30 days, or immediately, as running FFmpeg outside of the sandbox on untrusted input has been known to be a high-risk approach for way over a decade if not two. It's just to easy to find vulnerabilities in it and too hard to get stuff right in languages like C or ASM. 3. What's the exact alternative being advocated for here? Not reporting all the bugs because too many were found? Having people unfamiliar with the whole code base make patches (all 2 of them, or however many the exact research group that found the bugs had)? Having AI make patches? Or maybe keeping users in the dark and delaying telling them about security issues in the software they use (see next paragraph)? If a software project has security vulnerabilities, the approach is to inform the owners as soon as possible and - more importantly - the users within reasonable time, so they - if they wish to do so and are interested in doing so - are able to take precautions and apply workarounds. Arguing against N-day disclosure policies is arguing against allowing users to make informed choices wrt the software they run. And IMO 90 days is already too long for users to be kept in the dark - especially in 2026. Overall I don't think the FFmpeg crash out was valid. I am still happy that the FFmpeg project received some funding thanks to the whole drama though, and I would wish for it to be receiving even more from its large commercial users (but that's a different discussion and not achievable without a - probably impossible - switch to dual licensing).

LiveOverflow 🔴 hextree.io avatar
LiveOverflow 🔴 hextree.io@LiveOverflow·Nov 13

If you are a bug hunter and participated in the Cloudflare WAF, I would love to exchange our reports and methods. Maybe we can dig into them together and see how similar or different our methods actually were.

LiveOverflow 🔴 hextree.io avatar
LiveOverflow 🔴 hextree.io@LiveOverflow·Nov 13

I think a WAF CTF is amazing! @vercel did it in the past for react2shell and they were incredibly generous and fair to researchers. And so Cloudflare doing a similar effort for php2shell was great in principle! However, the way this was done leaves a bit of a sour taste for me

Post attachment
LiveOverflow 🔴 hextree.io avatar
LiveOverflow 🔴 hextree.io@LiveOverflow·Nov 13

So let's waste some more tokens and find a working B bypass. Took GPT-6 Sol ~2:30h until it adapted B AND got the flag on the live server. And you know what, the new bypass also "relies on the differences in how the Firewall and PHP recognise multipart headers." 🙀 who would have thought 🤷

Post attachment
LiveOverflow 🔴 hextree.io avatar
LiveOverflow 🔴 hextree.io@LiveOverflow·Nov 13

First, let's check if our reported bypasses get blocked. FYI, each exploit has four requests: A: OOM trigger to leave the stale object B: reclaim to leak address for ASLR bypass C: OOM trigger to leave the stale object D: reclaim for arbitrary code execution Turns out, our method 05, 03 and 06 only has request B blocked. Request A, C and D are still working! 05 and 03 were reported to Cloudflare and got the "Both reports rely on differences in how the Firewall and PHP recognise multipart headers." 06 I didn't report, because I have no @Hacker0x01 signal and I was out of trial reports. Imo the fact that CD still works, means the reported methods were not actually fixed. Making me even more suspicious of the "duplicate" claims. And because D works, it should also be possible to make B work again.

Post attachment
LiveOverflow 🔴 hextree.io avatar
LiveOverflow 🔴 hextree.io@LiveOverflow·Nov 13

The @Cloudflare php2shell WAF CTF has been incredibly frustrating. I had reported multiple bypasses and most of them got closed as duplicate of the same report, with an incredibly generic reason: "Both reports rely on differences in how the Firewall and PHP recognise multipart headers." d'uh! 😒 Of course many bypasses are going to be a parser differential between the WAF and PHP. That basically describes all WAF bypasses... So it felt a bit "scammy" to me. As if they just wanted o gather lots of bypasses, and marking them all as duplicates to avoid paying for each. Now Cloudflare has stopped the bounty reward for WAF bypasses. So let's see how the PHP2SHELL WAF rules hold up. 🧵 1/x

Post attachment
Chris Wysopal avatar
⟳ LiveOverflow 🔴 hextree.io retweeted
Chris Wysopal@WeldPond·Nov 13

Project Zero: Starting today, our policy is “Full 90”, i.e. vulnerabilities will be disclosed 90 days after they are reported to the vendor. On February 2, 2027, we will move to a “Full 60” policy where vulnerabilities are disclosed after 60 days. On January 3, 2028, we will move to a “Full 30” policy where vulnerabilities are disclosed after 30 days.

James Kettle avatar
⟳ LiveOverflow 🔴 hextree.io retweeted
James Kettle@albinowax·Nov 13

I'm seeing this too. A few years ago you'd get angry programs if you even thought about pivoting with a finding. Now it seems like some of them require you to break in, grab creds & pivot as far as possible.

Post attachment
s1r1us avatar
⟳ LiveOverflow 🔴 hextree.io retweeted
s1r1us@S1r1u5_·Nov 12

curious, how many 0days discovered by security researchers and later patched end up being exploited in the wild? for instance, how many chrome and firefox bugs demonstrated at pwn2own were later observed being exploited in the wild? i would assume very few. the whole point of proactive vulnerability research is to find and eliminate latent bugs before threat actors discover and exploit them. so im not sure why anthropic or openai vr impact is being measured by how many of its findings were exploited in the wild. isnt that the point of finding and patching them early?