- 2 Posts
- 12 Comments
krogoth@infosec.pubMto Pulse of Truth@infosec.pub•Microsoft wouldn't look at a bug report without a video. Researcher maliciously compliedEnglish6·2 months agoA tad late (the original story), but now there is an opinion piece on this topic now: https://www.theregister.com/2025/03/24/microsoft_opinion/
I like the part with “This a post-literate era, and we should expect the next demand for bughunters to express proof-of-concept as a TikTok dance short.”
krogoth@infosec.pubMto Pulse of Truth@infosec.pub•Hackers exploit DoS flaw to disable Palo Alto Networks firewallsEnglish2·5 months agoOH: «by sending a malicious DNS packet to the target device», 👌🤭
krogoth@infosec.pubMto Pulse of Truth@infosec.pub•Ivanti warns of maximum severity CSA auth bypass vulnerabilityEnglish1·5 months agoI lost count. How many vulns this year already?
krogoth@infosec.pubMto Pulse of Truth@infosec.pub•How Cloudflare CTO John Graham-Cumming cracked an encrypted ZIP file containing the code for a system that helped ANC members communicate safely under apartheid (Steven Levy/Wired)English9·7 months agoOr you could follow to the (original) blog: https://blog.jgc.org/2024/09/cracking-old-zip-file-to-help-open.html
krogoth@infosec.pubMto Pulse of Truth@infosec.pub•Revolver Rabbit gang registers 500,000 domains for malware campaignsEnglish1·10 months agoYou mean like FIST but with a huge revolver? 😍
krogoth@infosec.pubMto Pulse of Truth@infosec.pub•Majority of Critical Open Source Projects Contain Memory Unsafe CodeEnglish1·11 months agoNot sure if that is even the point. The article is all about memory unsafe programming!!1!. But there is no context at all.
Sure, there are vulnerabilities because of unsafe memory handling. But I looked for some statistic which would bring unsafe memory handling into context with say the high profile vulnerabilities from the last few weeks / months. I haven’t spent too much time on research but looking at some lists containing vulns from the last few months it seems as if all those pre-auth, priv escalation, directory traversal and whatnot very based on much simpler failures like wrong error handling or logical errors or missing code than unsafe memory handling.
I might be wrong, then please show me the numbers, but shooting at C/C++ because unsafe!!1! sounds like a very biased story there.
And while we are at it. I’d also be interested in C vs. (somewhat modern) C++.
krogoth@infosec.pubMto Pulse of Truth@infosec.pub•Zeppelin ransomware source code sold for 00 on hacking forumEnglish0·1 year agoWill have to look in the logs. Probably the pushing to Lemmy part.
krogoth@infosec.pubMto Pulse of Truth@infosec.pub•How to give Windows Hello the finger and login as someone on their stolen laptopEnglish2·1 year agoSurprisesurprise 🎉
News or not. I like the fact that the pot is calling the kettle black…