LiveOverflow πŸ”΄ hextree.io (@LiveOverflow) header
LiveOverflow πŸ”΄ hextree.io (@LiveOverflow) profile picture

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

Internet
Joined March 2015
Photo by LiveOverflow πŸ”΄ hextree.io (@LiveOverflow)Photo by LiveOverflow πŸ”΄ hextree.io (@LiveOverflow)Photo by LiveOverflow πŸ”΄ hextree.io (@LiveOverflow)Photo by LiveOverflow πŸ”΄ hextree.io (@LiveOverflow)Photo by LiveOverflow πŸ”΄ hextree.io (@LiveOverflow)Photo by LiveOverflow πŸ”΄ hextree.io (@LiveOverflow)Photo by LiveOverflow πŸ”΄ hextree.io (@LiveOverflow)Photo by LiveOverflow πŸ”΄ hextree.io (@LiveOverflow)Photo by LiveOverflow πŸ”΄ hextree.io (@LiveOverflow)Photo by LiveOverflow πŸ”΄ hextree.io (@LiveOverflow)
Where to find me: πŸ”΄ Hacking Videos: youtube.com/LiveOverflow πŸ“œ Articles: liveoverflow.com πŸ’» Start Hacking? liveoverflow.com/start-hacki… πŸ₯° Support: liveoverflow.com/support πŸ“Ή 2nd Channel: youtube.com/LiveUnderflow 🀳 Instagram: instagram.com/liveoverflow
15
108
1
670
LiveOverflow πŸ”΄ hextree.io retweeted
Replying to @haroonmeer
Thinking you can defend without understanding how one would break in is an equivalently common and similarly original sin.
4
7
1
27
3,163
what the fuck is going on
We have discovered NGINX2Shell, a pre-auth RCE in NGINX 1.31.8, the current mainline releaseπŸ’₯ This one came together in close work with @OpenAI, from discovery all the way through disclosure. Huge thanks to their team. More to come. #NGINX2Shell
18
17
3
549
35,913
I see the vision, but the term sucks. Can we find a better one :D
22
4
2
199
13,424
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
14
16
1
135
20,315
🚨 DON'T PANIC! 🚨 My Minecraft server was already UseAVX=2. So we are safe.
Java4Shell: write once, RCE everywhere calif.io/java4shell
2
4
126
8,124
LiveOverflow πŸ”΄ hextree.io retweeted
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
Replying to @OpenAI
GPT-6.2 Astra is our most capable model ever for cyber. It jumps 22 points over GPT-6 Astra on ExploitBench Internal Port. Due to increased capabilities, we’re launching GPT‑6.2 Astra and Sol with tighter safeguards for higher-risk cybersecurity assistance. We are working to bring these models to Daybreak so approved defenders can access them with reduced refusals.
15
23
1
147
14,710
I am in the market for AI liability insurance πŸ™ƒ
8
3
49
8,061
LiveOverflow πŸ”΄ hextree.io retweeted
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).
FFMPEG had one of the most valid crash outs in infosec history IMO. There's a huge elephant in the room when it comes to the fact that cybersecurity is extremely unbalanced. You have like 1,000 people pointing at problems for every 1 person fixing them. Vulnerability research is extremely important, but it's become somewhat of a marketing stunt. First with fuzzers, and now with LLMs. It's a lot of "look what my new toy can do" rather than earnest attempts at actually fixing security problem. What Google did to open source developers was especially egregious. They're a $3.6 trillion dollar company, who spent billions upon billions of dollars building a bot that points at problems really really fast, then they just dumped them all on a bunch of unpaid open source project maintainers to fix. Then because of Google's 90 day disclosure policy, the maintainers have 90 days to fix the issues. After 90 days, Google goes public with the issues, making their project look bad if the vulnerability is yet to be fixed, and also potentially harming users if it gets exploited. The 90 day policy was intended to give developers a reasonable amount of time to fix issues, while also applying some pressure with the threat of disclosure. Otherwise, you do get a bunch of goober ass vendors that will just ignore all security issues reported to them, then act completely surprised when their software gets hacked. But when you're a small team, non-profit, or a solo developer, and you have a trillion dollar company's AI just blasting you with infinite problems to fix (each coming with a 90 countdown & a threat), that becomes extremely untenable. They're essentially inadvertently blackmailing developers into becoming unpaid interns. Then on top of that, Google profits unimaginable amounts of money from the use of open source code. They use FFMPEG's code extensively across several highly-profitable products, meanwhile FFMPEG's developers work for free. There's no reason Google couldn't have donated money, engineers, AI tokens, or something towards fixing the problems. They can more than afford it. I don't think Google has any malicious intent at all, it's just that the whole incentive structure behind vulnerability research is completely whack. All the glory goes to people who find issues, not those who fix them, so there's not a whole lot of interest in helping with fixes. Some vulnerability researchers will submit fixes with their reports, but most don't. Honestly, in 2026 cybersecurity basically just feels like the equivalent of 50,000 people following the housecleaner around yelling "you missed a spot". Abysmally little effort has gone into anything outside of pointing out vulnerabilities.
6
11
108
18,023
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
21
33
440
35,261
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
1
3
56
4,940
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.
1
3
30
3,344
LiveOverflow πŸ”΄ hextree.io retweeted
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.
In the age of AI, 90 days isn’t fast enough. Today, Project Zero updated our disclosure policy to reflect the changes needed to protect users in this new world. projectzero.google/2026/11/d…
12
47
4
276
26,744
LiveOverflow πŸ”΄ hextree.io retweeted
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.
To bugcrowd, executing and extracting the output of "whoami" and "id" is not enough for an RCE. Not sure what does the team expect? Full explotation? to upload a shell? This is crazy, I just can't believe it @Bugcrowd
17
19
4
305
20,141
LiveOverflow πŸ”΄ hextree.io retweeted
amazing and gross. ty php
PHP allows bitwise XOR operation of strings so we can "create" words like system, id, curl... really useful for bypassing some challs that might be blocking strings
4
8
1
84
10,010
LiveOverflow πŸ”΄ hextree.io retweeted
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?
21
8
1
206
18,908
LiveOverflow πŸ”΄ hextree.io retweeted
I'm seeing articles about this every day (and including them in tl;dr sec for broader visibility). This is currently ongoing, not hype πŸ‘‡
Industry, please hear us. Autonomous attacks are here, at scale, breaching many organizations right this moment. Usually, with ARTEX and Cairn, usually through vulnerabilities. A thread Heather Adkins (@argvee) and I asked the industry to believe us…
2
10
1
68
8,825