I’ll be honest here.
I don’t feel the same excitement about iOS exploitation anymore like it was during the Lookout days in 2016 with the NSO exploit chains.
Today you can run commodity AI like DeepSeek, you run an AI swarm into a problem, it might cost you $3000 via API or nothing if you own some DGX, and you will find vulns. You will find the exact same vulns with $30,000 spent on openAI.
I think the only people left finding something are the ones building special fuzzing harnesses steered by an LLM to explore paths that weren’t explored before (there are already open source projects for this). And of course the upstream bugs that Apple keep introducing after each release.
Knowing that with an LLM you can reverse engineer anything end to end, plus you have access to better harness now and you can 1-shot your own:
Vulnerability research only constraints looks to be money (granted you have the skills already)
If you are rich you will find vulns.
If you are poor it means you missed all the previous cycles to make money on VR and you have a skill problem, or maybe you just started. If you just started it will be exponentially hard to find anything useful going forward the bar is extremely high and most importantly exponentially expensive.
Bad news for threat actors in cybercrime.
That leaves us with nation states or well funded firms / having resources to find new bugs.
If you are independent VR guy I wish you good luck.
Another Windows zero day released by Nightmare Eclipse (sort of)
It turns out Microsoft just straight up didn't patch an old CVE from 2020 correctly.
https://t.co/sNWBtTo4at
@TheHackersNews Confirmed: creates sections in SYSTEM-writable paths (FMPWinlogon1) with write access (0xf0007). The primitive is there. Missing from PoC: finding SYSTEM services that trust these sections for security decisions.
https://t.co/6Z5ms8b0Qk
@hetmehtaa I really liked your explanation of the “confused deputy sheriff” model!
Last night, however, I decided to run a reverse engineering analysis on the structure:
- UTF-16 SID at 0x10
- Local settings IDs (0x0409, 0x0410)
- GUID at 0x88
- Validated by WinDbg
https://t.co/6Z5ms8b0Qk
I reverse engineered the GreenPlasma Windows 11 primitive and found that CTFMON.exe stores user identity data inside shared section objects under:
\Sessions\1\BaseNamedObjects\
Including raw UTF-16 SID strings directly in memory.
https://t.co/CAXgNnwqiY