Kẻ soi mói

Hanoi, Vietnam
Joined October 2015
Janggggg retweeted
SharePoint + Pre-Auth RCE + MemShell? 👀 We’ve published our technical analysis of CVE-2026-65660, covering the attack chain from an Allow Anonymous site and a pre-auth SharePoint vulnerability to RCE and MemShell. Take a look: blog.viettelcybersecurity.co…
10
142
1
615
33,752
Thanks for speak out these words :)
i talked to a lot of people who played the defcon ctf finals to understand how llms affected them, both professionally and mentally. i went in hoping to learn that human intuition still mattered. instead, ctfs in their current form as everyone saying is dead, players are forced to operate slot machines because anyone who refuses to token-max loses to those who do. almost everything i learned, including how to learn, came from grinding ctfs. but the pipeline for developing that kind of skill and expertise now seems broken, juniors are rewarded for token-maxxing rather than going through the process of actually understanding things which is quiet sad and ctfs might not produce high quality security researchers any more. this also has serious implications for people who can’t afford tokens. five years ago, i wouldn’t have been able to afford access to something like gpt-5.6, and I would have been locked out of the very competitions that helped me build my career. anyway these are questions i asked if interesting for anyone: did they have fun? almost everyone was unhappy. it has largely become slot-machine operating, if they refuse to use llms, they lose to teams that do. it is not there is no fun at all, playing with friends and competing was all fun just process of solving which is main part and it isn't fun.(please let me know if you had fun) did having a skilled human in the loop still matter? i got mixed answers, but the leaderboard tells a fairly clear story, the top teams aggressively token-maxxed, by pooling gpt accounts and stuff. the #1 team allegedly spent around $50k on tokens xd. how much of the outcome came from human skill versus token-maxxing? its probably 95% token-maxxing and 5% human skill. some challenges, especially visual ones, remain difficult for llms, and human intuition to prompt mattered. but overall, the dominant strategy appears to be throwing more tokens at problems, one interesting observation, people who were better before llms were also better after the llms and they are the ones solving lot of challenges so it seems still 5% operating skill will put u in top and can't be dumb operator. will a new generation of players simply adapt to this new kind of competition? i thought maybe current players are just behaving like boomers who hate every new technology. but unlike previous technology stuff, there doesn’t seem to be much for the human to master here. token-maxxing is literally just token-maxxing. it doesn’t reward human ingenuity, it discourages it, and may eventually atrophies and makes us dumb let me know if i missed something or if you have different opinions
12
3,749
:) just for the meme
Pwn2Own Berlin 2026 took place quite some time ago, but only today have I had the opportunity to share details about our journey during the competition. This post focuses on analyzing a patched Windows LPE vulnerability. dungnm.hashnode.dev/pwn2own-…
1
25
3,111
gist.github.com/testanull/08… The PoC of SharePoint SE preauth RCE I still can't believe that MS replaced an old stable one with a new terrible design, come with multiple preauth vuln ¯\_(ツ)_/¯
6
58
2
288
36,056
Earlier this year I built out an unauth RCE chain against SharePoint, we disclosed it to Microsoft in May and today they have patched out the chains auth bypass vuln, CVE-2026-55040. Disclosure details on the @rapid7 blog, full technical details to be published at a later date...
In conducting a 0-day research project against #SharePoint, Rapid7 Labs discovered 2 new vulns that, when chained together, achieve RCE against a vulnerable server. Today, Rapid7 and Microsoft are disclosing CVE-2026-55040 – the first vuln in this chain: r-7.co/4f2HpQO
5
44
1
172
32,226
Found an RCE in a popular OTT app - patched fast via responsible disclosure. Thanks to VSRC & Zalo Security for the quick fix 🙏
9
45
386
32,126
Janggggg retweeted
[ZDI-26-331|CVE-2026-45495] (Pwn2Own) Microsoft Edge Feedback Log File Handling Directory Traversal Remote Code Execution Vulnerability (CVSS 7.5; Credit: Orange Tsai (@orange_8361) of DEVCORE Research Team (@d3vc0r3)) zerodayinitiative.com/adviso…
12
59
6,036
There it is! Orange Tsai (@orange_8361) of DEVCORE Research Team was able to exploit Microsoft Exchange! If confirmed, they win a whooping $200,000 and 20 Master of Pwn points. Off to the disclosure room to explain how they did it and seal the deal. #Pwn2Own #P2OBerlin
15
63
18
519
68,797
Janggggg retweeted
Patch your Linux boxes! Copy.Fail is a trivially exploitable logic bug in Linux, reachable on all major distros released in the last 9 years. A small, portable python script gets root on all platforms. Found by the teams at @theori_io and @xint_official More details below xint.io/blog/copy-fail-linux…
21
356
64
975
255,456
We promised we'd be back! Join us on our journey, from repro'ing N-days to stumbling into 0-days in SolarWinds Web Help Desk, eventually achieving pre-auth RCE. This research fuels the watchTowr Platform, our Preemptive Exposure Management technology. labs.watchtowr.com/buy-a-hel…
67
5
206
40,846
Janggggg retweeted
Ever wondered what happens when you pickle a mailbox? 🥒📬 (No, it’s not a recipe, it’s a vulnerability.) Our team breaks down CVE-2025-20393 in a new deep dive post covering root cause, internals & exploitation details starlabs.sg/blog/2026/01-pic… Written by @CurseRed & @bestswngs
1
28
1
86
9,282
testbnull.medium.com/and-the… My note while trying to reproduce the famous react2shell bug, no WAF bypass and bugbountytips inside, I promise ;) Happy reading!
1
48
180
30,416
Janggggg retweeted
Oracle Cloud was breached in Jan 2025 through vulns in Oracle Access Manager. @SLCyberSec's Research team found a new pre-auth RCE vulnerability in Oracle Identity Manager (CVE-2025-61757). This is a critical vulnerability and is trivial to exploit. slcyber.io/research-center/b…
39
159
14,862