@faker it always amused me where people were up in arms about China having a law to force vuln disclosure to their government prior to public disclosure... when the US already does that.
@badsamurai they do! but they also keep firing people and freezing recruitment (happened on the Windows engineering team too), so it's quite hard to fix something when nobody will pay for it.
Another thing I'd say is apply pressure to Microsoft to fix the root cause of these kind of issues.
I think I've told the story before around DWM priv esc, where one came into MS and we sat on the call to the engineers and they went 'yeah, there's thousands of these in DWM that we know of. We fixed this one.'
Why didn't they fix the rest? Resource. Easier to just play whackamole each month.
MS currently world's biggest org in stock market, they can afford to invest in Windows security.
Personally I wouldn't rush around patching zero days in Windows for priv esc every time you see a headline, as
a) there's one almost every month now
b) this is something like the 6th in CLFS alone
c) you're patching months (and in some cases years) after ransomware groups started using said privilege escalation exploit - your risk horse already bolted
So just keep calm and patch as usual. Wider question is how to stop people getting endpoint access.
In a similar thing, you can see Black Basta running around with a local priv esc vuln in Windows for several months in this thread below.
The pattern is basically ransomware groups can afford to buy or pay to develop local user -> local admin exploits, and not be discovered for extended periods of time.
From a defence point of view, assume ransomware groups can easily get local admin rights - and don't pay ransoms as it is directly funding the problem for all.
Regarding CVE-2025-29824, the vuln in CLFS linked to a ransomware group.
First off, Microsoft write up is good (aside from the eyeroll attempt to sell Copilot, using no useful functionality).
Also, blog actually mentions it's a zero day - MS need to keep _consistently_ calling zero days in its own products zero days.
Microsoft don't say when exploitation started - but I just crawled some EDR telemetry with a friendly vendor, looks like it goes back at least 9 months.
This is so much jedi mind tricks it should be framed in a gallery - they managed to disclose a cybersecurity incident without saying cybersecurity or security or even what was compromised.
> In recent weeks, the Administration and Congress have made significant changes that threaten to negatively impact vital lupus research, drug development and public health initiatives, including the reorganization and significant staff reductions at the U.S. Department of Health and Human Services (HHS) and cutting the Lupus Research Program at the Department of Defense (DoD).
More from @lupusorg and how to take action yourself to protect Lupus research:
I watched a YouTube video earlier of Big Brother in Germany informing housemates of COVID-19 for the first time, and now the algorithm is feeding me all the world’s Big Brother contestants finding out.
The videos are.. quite surreal. Ones like, Brian arguing about cereal.. then Brian finding out 30k people are dead, then Brian crying because the show got cancelled and now he can’t be on TV.
Cybersecurity weather person and award winning shitposter. Shitposting is an anagram of Top Insights. You may be surprised to know I am not representing my employer here and these are not their opinions.I have Direct Messages disabled - you can send them, but I will never receive them.