* Unauthenticated RCE vs all GNU/Linux systems (plus others) disclosed 3 weeks ago.
* Full disclosure happening in less than 2 weeks (as agreed with devs).
* Still no CVE assigned (there should be at least 3, possibly 4, ideally 6).
* Still no working fix.
* Canonical, RedHat and others have confirmed the severity, a 9.9, check screenshot.
* Devs are still arguing about whether or not some of the issues have a security impact.
I've spent the last 3 weeks of my sabbatical working full time on this research, reporting, coordination and so on with the sole purpose of helping and pretty much only got patronized because the devs just can't accept that their code is crap - responsible disclosure: no more.
back in 2013, @sima published a i915/GEM Crashcourse explaining the Linux kernel i915 GPU driver; I read that earlier this year, and it was really helpful for understanding what is going on in the i915 code and understanding the context of CVE-2024-42259.
I think without that explainer, it would have taken me a long time to understand what GTT MMIO mappings are. The idea that some physical address region owned by the GPU proxies physical memory accesses based on GPU page tables is pretty mindblowing...
Oh those sneaky bastards. I moved to moderated registrations on Infosec.exchange where new signups have to enter a reason for joining. That’s turned out to be a very good filter. Until now.
I just suspended an account for spam and looked at their reason for joining which was this:
I’m a cybersecurity enthusiast with a background in [your background, e.g., IT, software development]. I’m keen on sharing knowledge, staying updated on the latest security trends, and engaging with professionals in the field. I want to contribute to discussions on best practices and learn from the community to enhance my skills. Thank you for considering my application!
I wasn’t overly picky about reasons for joining - if it seemed like an actual person that was here for some reason other than marketing, seo, etc, I’d approve it. But this reason is clearly generated by an llm, and gave them an instruction to replace some text in brackets, which they did not do.
KVM Forum 2024 is being live streamed!
https://www.youtube.com/live/0P_vLo9IHBw?si=w13Aj_9X-OYMJO3K
Your efforts in saving energy matter!
"An AI-generated bot account was able to comment “PUSSY IN BIO” on 2.1 million Instagram posts, all thanks to you switching from AC to a big box fan that just kind of pushes the stale, hot air in your apartment around. We’re building a better world—together."
Here are the slides of my "Simple Machine Learning Techniques for Binary Diffing (with Diaphora)" talk given at the @44CON conference last week:
https://github.com/joxeankoret/diaphora-ml/blob/main/docs/diaphora-ml-techniques-44con-final.pdf
#44con #Diaphora #MachineLearning #ReverseEngineering #BinaryDiffing
Open to Exploitation: The Security Risks of Unauthenticated Pager Networks https://telescope.ac/petazzoni/kl9ki6zsn62bsb03l694dz
Binwalk v3 now under active development. Faster, smarter, Rustier.
Beta testers and bug reports welcome!
Working on some photos and videos from our ribbon cutting event for the new Adafruit factory in Industry City, Brooklyn, NY - USA! Here's a preview! 🎀✂️🏭🗽🇺🇸 Special thanks to the President of the Brooklyn Chamber of Commerce, the Managing Director of Industry City, and the Vice President of Partnerships at the NYC EDC! More soon, it's Sunday after a loooong week and we are zonked!
This is crazy. Someone managed to run #Linux (v4.4) on an #Intel 4004 #CPU from 1971, one of the first commercially available microprocessors ever.
The craziest part: It became possible by writing a #MIPS #R3000 #emulator in 4004 #assembler that fits into the 4096 bytes¹ of addressable memory. The emulator then runs the kernel. My mind is blown.
https://dmitry.gr/?r=05.Projects&proj=35.%20Linux4004
¹) The memory was eventually expanded to 8192 bytes via some bank switching trickery as the article explains
Two rules (from @getsentry who started this):
1. Give money to the open source projects which are probably 90% of your code base. $2000 per developer on your staff, although you can and should do better than that. (@buttondown are doing better than that.)
2. Report every year on whether and how you did it.
This seems like a good idea today, and a thing where non-participation should feel weird tomorrow.
PoC Exploit Released for Windows Hyper-V Zero-Day Vulnerability CVE-2024-38080 https://securityonline.info/poc-exploit-released-for-windows-hyper-v-zero-day-vulnerability-cve-2024-38080/
Personal update: if you need a guy who is passionate on innovative in-the-wild zero-day exploit detection and advanced vulnerability research, please let me know. DM open. :)