Exploring the world with my sword of debugger : )

Joined August 2013
Love the gifts from @Apple Product Security! ❤️❤️❤️
17
24
2
1,234
68,516
Will share one of them at the Nullcon Berlin @nullcon
4
1
49
22,219
I just got 16 new CVEs in this new release 🤣🤣🤣
20
21
3
533
34,609
I got 14 new Apple CVEs in this release😎
🐛 NEW SECURITY CONTENT 🐛 💻 macOS Sequoia 15.4 - 131 bugs fixed 💻 macOS Sonoma 14.7.5 - 91 bugs fixed 💻 macOS Ventura 13.7.5 - 85 bugs fixed 📱 iOS and iPadOS 18.4 - 62 bugs fixed 🥽 visionOS 2.4 - 38 bugs fixed 📱 iPadOS 17.7.6 - 38 bugs fixed
17
37
3
645
52,543
Finally got a reply from Parallels (Alludo), only after the 0-day is dropped. Should I remove the post?
New 0 day dropped: jhftss.github.io/Parallels-0… Conclusion: 1. Don’t trust @thezdi , they are too late to handle our reports. One of my reports was submitted in 2024 Jan, but it is still not disclosed to the vendor. No reply from the ZDI yet! 2. Don’t trust the Parallels security!
19
13
1
113
36,217
“tss_should_crash=0” doesn’t work on XNU production build now :(
So, if your debugger crashed in the API “task_set_exception_ports” or “thread_set_state”, try to use the boot args: sudo nvram boot-args="thid_should_crash=0 tss_should_crash=0"
2
1
1
26
7,538
So, if your debugger crashed in the API “task_set_exception_ports” or “thread_set_state”, try to use the boot args: sudo nvram boot-args="thid_should_crash=0 tss_should_crash=0"
4
10
1
61
20,544
macOS Sonoma patched about 10 reports of mine. But only 2 CVEs are published. 4 of them are newly introduced vulnerabilities in macOS 14 beta version. The weird thing is that Apple removed the CVE entries that they assigned before and put them in Additional Recognitions. 😳😳
11
10
2
89
39,547
It wasn’t until Apple asked to review my slides that I realized @defcon had accepted this topic. I tried to contact them last month, but got no response. Really bad experience, isn’t it? 😳 So I decide to give up DefCon and make my debut at #OBTS
6
5
1
67
17,900