I haven't even had my first cup of coffee and we have another ../ CVE. This time it's Synology: https://nvd.nist.gov/vuln/detail/CVE-2024-11398
Exactly 11 (!) years ago we released an advisory for an rsync 0-day.
Two days earlier the Gentoo Linux mirror I was hosting and maintainig was compromised with it.
What a ride.
https://forums.gentoo.org/viewtopic.php?t=111779
https://lists.samba.org/archive/rsync-announce/2003/000011.html
Maybe fun to know - using #MS365 means that the US government has bulk access to your data, which matters if you are a government yourself. Supporters of Microsoft will tell you you can easily use "double key encryption" to protect your MS365 data against US government snooping. This is how easily you can do that. Hint, it involves GitHub and compiling code: https://learn.microsoft.com/en-us/purview/double-key-encryption-setup
My VirusBulletin presentation: A web of surveillance was uploaded to YouTube: https://www.youtube.com/watch?v=iERGg1dUVNE
New whitepaper and exploit code from @stephenfewer on 5 new vulnerabilities he chained to achieve unauthenticated RCE on Lorex 2K Indoor Wi-Fi security cameras. The exploit works in two phases and comprises an auth bypass, a stack-based buffer overflow, an out-of-bounds heap read, and a null pointer dereference — and that's just to start (because it was, like, Tuesday for Stephen or whatever) 📈
Interestingly enough, MS disabled the "Use my Windows user account" checkbox when connecting to Wi-Fi on the lock screen to address CVE-2024-38143 in the August Patch Tuesday.
This change completely remediates the "Airstrike" attack as well. 🤯
DNA Lounge Update, Wherein we negotiate with the mob
https://www.dnalounge.com/backstage/log/2024/12/03.html
The Advent of Code for V has started, uncovering a new challenge every day! Check them out!
Unused functions are now skipped by default. This reduces generated C dramatically. Give it a try! if you have issues, use v -no-skip-unused ... and report them.
After making this option by default, CI times went down significantly:
I've noticed a concerning trend of "slop security reports" being sent to open source projects. Here are thoughts about what platforms, reporters, and maintainers can do to push back:
https://sethmlarson.dev/slop-security-reports?utm_campaign=mastodon
Fucking PaloAltoNetworks...
two major CVEs come out, guidance says X version is fine and unaffected. I upgrade everything to that version.
PaloAlto then changes the CVE details to say that ""LOL version Y is good, X sucks.""
I don't want to have to keep checking CVE pages for changes....