0xaeced

[Microsoft Security Response Center @msftsecresponse]

Over the past several days, we have been listening to the conversation around coordinated disclosure and the relationship between security researchers and vendors. We recognize that this relationship is both critical and, at times, fragile. We deeply value the security community, and will continue to take your feedback seriously.

To be clear about our approach to legal matters, we have no intention to pursue action against individuals conducting or publishing their security research. When an individual breaks the law and engages in malicious activity causing real harm to our customers, we will work with law enforcement as appropriate.

We recognize the work that goes into researching and submitting a vulnerability. We are committed to approaching every interaction with transparency, clear communication, and professionalism. We continue to believe strongly in Coordinated Vulnerability Disclosure as the foundation for protecting customers and improving our products. Each year we process a high volume of vulnerability reports. That volume continues to grow and will continue with the rise of AI-enabled research. We acknowledge that some interactions have fallen short and are working to learn from them.

Many of us have experience on both sides of this work, as researchers reporting vulnerabilities and as responders triaging and assessing them. That perspective informs how we approach this feedback and the importance we place on getting it right, particularly as the volume and complexity of research continues to grow.

The security community plays a vital role in helping us protect customers. We are committed to maintaining a constructive and respectful relationship and growing together. We know that, given the nature of this work, there will at times be misunderstandings. We remain committed to engaging in good faith and to providing a respectful and professional experience for all researchers, regardless of past interactions.

[0xaeced @dec_eax]

Start of new era...
https://t.co/9lzL4dkzQx

[Google VRP (Google Bug Hunters) @GoogleVRP]

📣📢 Calling all Android and Chrome bug hunters 🧑‍💻🔎!

We're updating our Android & Chrome VRP programs to ensure we can continue to reward the most challenging and impactful vulnerabilities researchers find in our products. For details, 👇

https://t.co/hyZzEIampk

[0xaeced @dec_eax]

Interesting story related to Trenchant
https://t.co/jHm3pAtW6N

[0xaeced @dec_eax]

One more
https://t.co/1K3Rt5hYfe

[0xaeced @dec_eax]

Operation Zero(@opzero_en) and Advanced Security Solutions(@advance_sec0) have been sanctioned by @USTreasury
https://t.co/Tw6YYhJaCG

[0xaeced @dec_eax]

Interesting...

[0xaeced @dec_eax]

CVE-2025-9864 v8 use-after-free exploit by @r1ngz3ro
https://t.co/MSmsCoFfas

[Crusaders of Rust @cor_ctf]

Say hello to Eternal Tux🐧, a 0-click RCE exploit against the Linux kernel from KSMBD N-Days (CVE-2023-52440 & CVE-2023-4130)

https://t.co/Cbk9MBo91v

Cheers to @u1f383 for finding these CVEs + the OffensiveCon talk from gteissier & @laomaiweng for inspiration!

[0xaeced @dec_eax]

3/3 Nobody should send exploits to them. Otherwise, you won't get paid or your exploits will be used by malicious actors definitely.
If you want to know more details or to look for reliable entities, reach me anytime.

[0xaeced @dec_eax]

1/3 Recently I have investigated several entities promoting themself as companies purchasing 0day exploits including @advance_sec0, @tn__sec and others.
Most of them should not be trusted because they are not legal companies and similar to scammers.

[0xaeced @dec_eax]

2/3 For example, @advance_sec0 is the replacement of Vulns Security which is inactive and disappeared already. The company is registered nowhere and they are even trying to resell exploits on dark web instead of working with government entities. They will also disappear soon.

[Smukx.E @5mukx]

Understanding Arbitrary Access Primitives in Windows Kernel

https://t.co/e2Y61EERXV

[xvonfers @xvonfers]

[$55000][380397544][wasm]Arbitrary WASM type confusion due to improper fix of b/379009132

PoC:
https://t.co/OnOVISvZaJ

Exploit that pops calc(Windows x64, Canary 133.0.6853.0):
https://t.co/FsRDhgOpzm

@0x10n

[TyphoonCon🌪️ @typhooncon]

🌪️ TyphoonPWN is back for its 7th year — and we're targeting Microsoft Exchange Server!

💰 Up to $80,000 USD for valid RCE exploits
🧠 Open to researchers, pentesters & vuln hunters
💻 Remote participation welcome
Secure your spot: 👉 https://t.co/DnrRqqQuFB

[Orange Cyberdefense Switzerland @orangecyberch]

🛡️ In this blog post, @itm4n and @PMa1n extend the work of @floesen_ and demonstrate how Server Silos can be leveraged to exploit the #KsecDD #Windows driver, and achieve #admin-to-kernel even when LSA Protection is enabled.

👉 Discover more about it: https://t.co/KnwKlWlRYy

[LukeGix @LukeGix]

I published a post describing the exploitation process for CVE-2024-38193, a use-after-free vulnerability in the afd.sys Windows driver. Hope you enjoy it! :)

https://t.co/tzazvZxOqp

[Alexandre Borges @ale_sp_brazil]

The fourth article (126 pages) of the Exploiting Reversing Series (ERS) is available on:

https://t.co/Vf0FnwfyiK

I would like to thank Ilfak Guilfanov @ilfak and Hex-Rays @HexRaysSA for their constant and uninterrupted support, which have helped me write these articles.

The fifth article (ERS 05) will be released soon. Stay tuned.

I hope you enjoy reading it and have an excellent day.

#apple #ios #macos #architecture #cybersecurity #research #internals #vulnerability #idapro #informationsecurity

[Nicolas Krassas @Dinosn]

Windows Sockets: From Registered I/O to SYSTEM Privileges https://t.co/09yzW6CE7r