Is #Microsoft #Defender for #Identity part of the #MSRC #Bounty program?

Asking for a fried.

A deep dive into CVE-2023-2163: How we found and fixed an eBPF Linux Kernel Vulnerability

https://bughunters.google.com/blog/6303226026131456/a-deep-dive-into-cve-2023-2163-how-we-found-and-fixed-an-ebpf-linux-kernel-vulnerability

Confusion Attacks: Exploiting Hidden Semantic Ambiguity in Apache HTTP Server!

https://blog.orange.tw/2024/08/confusion-attacks-en.html?m=1&s=09

Latest by Orange Tsai!

W00t! @hdm / @runZeroInc made sshamble public (took forever for BH/DC to get here).

https://github.com/runZeroInc/sshamble

SSHamble is research tool for SSH implementations that includes:

— Interesting attacks against authentication
— Post-session authentication attacks
— Pre-authentication state transitions
— Authentication timing analysis
— Post-session enumeration

Gorgeous website for it too: https://www.runzero.com/sshamble/

FTX settles complaint from the CFTC with $12.7 billion payout

August 8, 2024
https://www.web3isgoinggreat.com/?id=ftx-cftc-settlement

"Question regarding you hacking my webserver?"

It is #inbox time again.

https://bagder.github.io/emails/2024/2024-08-07.html

A new post by #CrowdStrike refutes some claims I amplified earlier:

https://www.crowdstrike.com/blog/tech-analysis-addressing-claims-about-falcon-sensor-vulnerability/

Some notes:
- seems CS can't update through middleboxes. This is an unusual design but makes sense IMO (screw middleboxes!)
- "Before loading the channel file from disk, the Falcon sensor verifies that the file contents match the expected hash to detect any local modifications of the file." Sounds like a TOCTOU, but that's just a wild guess

Thrilled to announce that, after roughly 4 years of dedicated collaboration between Mozilla and Google's WebDriver automation teams, Firefox is now officially supported in Puppeteer, thanks to the new WebDriver BiDi protocol!

This significant milestone allows seamless testing of websites in Firefox, using tools that were previously exclusive to Chrome.

Please share your thoughts and feedback, let us know what works and what features you'd like to see!

https://fosstodon.org/@planetmozilla/112921805158708461

Protip: You can also make a phone call by holding it up to your ear and speaking into it directly at a low volume.

Thanks to @jmc for setting it up, there's a new mailing list for those interested in all aspects of illumos on SPARC

https://illumos.topicbox.com/groups/sparc

Nothing there yet, but I thought I would give those interested a chance to join before starting up some conversations

💫DID YOU KNOW💫
that if you move a mouse cursor fast enough, you can get persistence of vision and, say...
*run a game of Pong inside your mouse's firmware*
🕹️🕹️🕹️🕹️🕹️🕹️🕹️🕹️🕹️

ClownStrike.lol now says #Fortinet has falsely blocked the domain as "phishing" and is giving them the runaround about appealing it. This domain is demonstrating all of the cybersecurity industry's problems. https://clownstrike.lol/crowdmad/

CPU bugs reached a level of yikes that speculation side channels can only dream of

https://ghostwriteattack.com/riscvuzz.pdf

Tony Hawk's Pro Strcpy https://icode4.coffee/?p=954

This tabloid cover feels cyberpunk in a good way #adtech

The whitepaper is live! Listen to the whispers: web timing attacks that actually work. Read it here ->
https://portswigger.net/research/listen-to-the-whispers-web-timing-attacks-that-actually-work

Ivanti and Fortinet have unpatched vulnerabilities in their VPN products!
Akamai, in their blog post Living off the VPN — Exploring VPN Post-Exploitation Techniques, talk about techniques that can be used by threat actors after compromising a VPN server to further escalate their intrusion. The key takeaway is that the vulnerability disclosure was published 133 days after initial notification to Ivanti and Fortinet:

• CVE-2024-37374 (unknown CVSS score) Ivanti hard-coded key issue?
• CVE-2024-37375 (unknown CVSS score) Ivanti MDM cleartext passwords issue?
• Fortinet custom encryption key bypass issue (no CVE ID assigned)

Fortinet informed us that after additional consideration, they decided to not fix the custom encryption key bypass as it “does not cross a security boundary”

If the original Ivanti Connect Secure exploited zero-day fiasco hasn't scared you off of their products, this is your wakeup call. As @cadey would say: "No way to prevent this" say users of only VPN where this regularly happens

cc: @campuscodi (who else wants to be notified of issues like this?)

#CVE_2024_37374 #CVE_2024_37375 #Fortinet #Ivanti #ConnectSecure #FortiGate

“Variant analysis is the lowest effort, highest reward activity for preventing 0days” @natashenka

Another year, another Microsoft Most Valuable Researcher for me. This year, it has a bittersweet taste though.

Let’s kick off with the sweet part.

I’m quite happy with my consistency and findings. My record for 2024:
- 10x Exchange
- 2x SharePoint
- 1x .NET/VS

Multiple RCEs included.

I have also already reported several vulns for 2025, and I’m happy with the technical level of the findings. Not necessarily with the impact, but you don’t always get RCE;). I’m especially happy with the fact that I’m doing some risky deep dives, and sometimes it pays off.

I’m also happy with some recent research. I’ve been abusing unknown attack surfaces and I had some success with that (even though I was not familiar with the target). At least some of them are unknown according to my knowledge, so even if they are known, it does not count, right? :)

Now the bitter part.

Over the entire year, I had an impression that MSRC leaderboard is missing points for the majority of my submissions. I was signalizing this issue a couple of times, but with no effect. I was even not on the initial MVR list.

After my small tweet, some of my missing points were found and I eventually made it to the list (thx MSRC for this intervention). The truth is – the list is not so important to me. I like to think about vuln disclosure as some mutually respected process.

I’m not collecting bounties (reporting as ZDI) and the only thing I want in return for my submissions is a proper acknowledgment. I think that this process failed in 2024, but I hope it will eventually get better. I have impression that I should have way more points, but whatever.

Another part – several of my submissions were rejected as an expected behavior. Not a nice feeling, but it’s a part of the game. I can see a lot of tweets about dropped submissions and this part concerns everybody. From my perspective, reporting of .NET vulns is hardest.

I have a small perception that if you cannot exploit something that you consider a .NET vuln in Exchange or SharePoint, it’s probably going to be ignored (based on my experience only). Well guess what, there are different products/apps based on .NET too :D

To sum up, quite a good year. Hoping to have an even better 2025, although my Exchange run from 2023/2024 will be hard to repeat.

I hope to deliver some nice research and to see you next year during conferences or wherever. Cheers

Fresh root cause analysis by #CrowdStrike

https://www.crowdstrike.com/wp-content/uploads/2024/08/Channel-File-291-Incident-Root-Cause-Analysis-08.06.2024.pdf