Responsible disclosure has given me so many headaches over the past few months. Dealing with vendors took longer than finding and documenting the vulnerabilities.
Remember: Vendors must act responsibly, too! Otherwise, discoverers will tend to return to full disclosure.
Things are getting fun: Teach agents how to find sources/sinks, do static taint analysis with our #Binja plugin #Mole, and triage paths with live/emulated target access to validate findings autonomously. Reported 2 new vulns: remote unauth. stack BOF + auth. OS command injection.
Similar experience with responsible disclosure for #ArgoCD.
Reported a blind SSRF vulnerability back in January (clearly less critical than Synacktiv's findings), but so far the only visible action has been assigning the GitHub Advisory a "Triage" label.
CI/CD pwnage with a pre-auth RCE in #ArgoCD by @hugow_vincent ๐ฅ
Discover how a single misconfiguration in a Helm chart can lead to a full cluster compromise sprinkled with some CodeQL shenanigans! ๐ฅท
https://t.co/bNH8rE7uNo
We analyzed how different LLMs and prompt strategies impact bug triage performance in our #BinaryNinja plugin #Mole. TL;DR: Real-world code is far harder than synthetic benchmarks, false positives dominate, stability varies by model, and prompt tuning is strongly model-dependent.
First two unauthenticated RCE CVEs published - Discovered with the help of our #Binja plugin #Mole!
๐ Advisory: https://t.co/tgb42PVnyx
๐ Mole: https://t.co/J3NwT2iWkK
More vulnerabilities have been reported - stay tuned for upcoming advisories.
Static pointer tracking is tricky.
Just shipped some improvements to my #BinaryNinja plugin #Mole: it now tracks array and struct members more precisely.
An example on how Mole does this: https://t.co/4FQOPA1l1F
Binja's multiple ILs make precise analysis so much more powerful!
A while back, I wanted to learn about @qb_triton and symbolic execution in general, and to research its challenges when it comes to real-world binaries. What began with a few simple scripts evolved into PoC tool called Morion, which I've just released.
#symbex#libtriton#morion
I've written a detailed showcase to highlight some of the tool's features (and current limitations). The showcase illustrates how the tool can, for example, help assess if a bug is exploitable and if so, assist in crafting a functional exploit:
https://t.co/zPviKloeiW
@HatforceSec@cydcampus@IEEE The paper should soon be listed on the conference website: https://t.co/cuvmX68J3Z. Give me a DM if you want me to share it directly.
You missed the interesting @swisscyberstorm talk "Hidden Inbox Rules in Microsoft Exchange" by @dp__pd? All infos about his research and the attack can be found here: https://t.co/M7zfbRiUZu #SCS18