All 5 zauth findings are fixed and live. Great job @willhasroot, and thanks for the findings.
- Rate limits could be dodged
- Memory could be flooded
- Lists could be overloaded
- Helius key could be overused
- DEX quotes hit Jupiter's free tier
None put funds or keys at risk.
doing a lot of multitasking right now, but wanted to share some progress on our new landing page and product demo. fully e2e interactable Vector setup to show you just how easy it is for Vector to scan or pentest your web app, API, codebase, or smart contract.
and yes - we will be honoring the "if we cant break in, its on us" policy on this release. meaning that if Vector produces 0 findings of high or critical severity, every penny of the scan is covered by us.
while we want to keep Vector fully autonomous, we will be adding an option where you can opt for an additional human review for that extra peace of mind for your project. this will be auto applied for codebases > 200k SLOC, and > 100k SLOC for smart contracts (which are still coming soon).
we have argued and have published reserach regarding how Vector is the most powerful pentesting platform in its class - its time for you to see it for yourself, completely free if we find nothing.
0click 0auth RCE in uvdesk, found fully autonomously under project apex with @zauthinc.
73 days since disclosure and no response so heres the PSA and POC 🤷♂️
apologies for the absence on here the past few weeks. i’ve been heads down on development and our client load instead of social media, but i’ll get back to posting more frequent updates. you can join the discord for direct contact with me and the team, link in the replies.
as some of you know, we’ve been privately auditing smart contracts for customers and for bounties over the past 3 months. i’ve spent over a month and thousands of dollars getting this software ready to release to the public. our smart contract auditor will work the same way as vector, our pentesting engine. self serve, no human intervention, priced per sloc. when it’s in my own hands i’m confident this is one of the most capable auditing models on the market, but full autonomy is the hardest part. it’s why auditing companies require sales calls and contact before any agreement, and it’s why audits are so slow and expensive. changing this workflow is the whole point of what we’re building at zauth.
right now i’m testing vector by feeding it historical hacks. we’re blind testing it against every major smart contract exploit that’s ever happened. if it wouldn’t have caught the vulnerability in an audit, our tooling isn’t good enough yet. we rewind the chain to the block right before each exploit and hand it the source that was deployed at that moment, with no answer key and no hints. it has to locate the bug and construct the drain under the same conditions the original attacker faced. identifying the type of bug is close to solved. the hard part is proving you can actually drain it. that means chaining the contracts together the right way, blind, on a real fork, and doing it reliably on large codebases. that’s where most of my effort is going.
we plan to release in two stages. evm first, currently covering ethereum, bsc, base, arbitrum, polygon, robinhood chain and more. solana will follow, since it has a completely different runtime and a different exploit model.
reinventing how security gets done is no small task, but if you look at what zauth has delivered over the past 10 months you’ll see why i quit my job and went full time on zauth. i am betting everything on us winning.
When pentesting with zauth, you have two options.
a) 50 dollars for a black box test. Our agents attack your web app with nothing but the URL.
b) 150 dollars for a full source code audit.
Nobody does a real pentest for 50-150 dollars. We make cybersecurity accessible.
Our first ever GitHub advisory is live, in DragonflyDB.
One flag, with one call site. deep_integrity was set for RESTORE and nothing else, so replication and RDB file load ran the same deserializer with validation off. Malformed listpack loads clean, HGETALL segfaults the server, or leaks adjacent heap (if you shape it like that), 19/30 runs, live pointers.
Found autonomously by Project Apex. Disclosed Sep 1, fix merged Sep 17, published today by DragonflyDB team.
github.com/dragonflydb/drago…
Large incumbent companies are incredibly slow at handling cybersecurity related disclosures.
Reports are important, but they are irrelevant when teams take days, weeks, or months to respond.
Take personal opsec seriously, because companies often don't.
Cyber is having a moment
Across 21 major software companies, including Apple, AWS, Microsoft, and Google:
- Reported critical vulnerabilities never cleared 100 per month in four years
- Since spring they've jumped to over 600 per month
Charts of the Week: a16z.news/p/chart-of-the-wee…
been a busy weekend leading into an even busier week.
we've now disclosed four critical vulnerabilities under Project Apex, all found autonomously by Vector.
I've written and recorded PoCs for all three, but they stay private until they're fixed. the second they are, everything goes public. these impact millions of users cumulatively.
Vector is not finding theoretical issues in toy apps. it is finding the highest severity vulnerabilities in real software that real people depend on, faster than a human team ever could, in code that has been public and reviewed without anyone catching it.
we've also updated the zauth landing pages and docs.
CLI is coming along and it will be amazing. more on that soon.