I struggle to understand the issue .. could someone help me out ? Ok, you got " https://discord.com/_mintlify/_static/hackerone-a00f3c6c/lma... " to send a controlled payload But regular users will never hit " https://discord.com/_mintlify/_static/hackerone-a00f3c6c/lma... ", so they will never execute your script I fail to understand how this can be exploited, by whom and in what conditions
We pwned X, Vercel, Cursor, and Discord through a supply-chain attack
61–70 of 453 posts
Re: We pwned X, Vercel, Cursor, and Discord through a supply-chain attack
#62Seems like such a tiny amount of money for a bug that can be used to completely own your customers accounts. Also not much excuse for xss these days.
This comes up on every story about bug bounties. There is in general no market at all for XSS vulnerabilities. That might be different for Twitter, Facebook, Instagram, and TikTok, because of the possibility of monetizing a single strike across a whole huge social network, and there's maybe a bank-shot argument for Discord, but you really have to do a lot of work to generate the monetization story for any of those. T…
In the end, you are trying to encourage people not to fuck with your shit, instead of playing economic games. Especially with a bunch of teenagers who wouldn't even be fully criminally liable for doing something funny. $4K isn't much today, even for a teenager. Thanks to stupid AI shit like Mintlify, that's like worth 2GB of RAM or something.
It's not just compensation, it's a gesture. And really bad PR.
Re: We pwned X, Vercel, Cursor, and Discord through a supply-chain attack
#63This feels so emblematic of our current era. VC funded vibe coded AI documentation startup somehow gets big name customers who don't properly vet the security of the platform, ship a massive vulnerability that could pwn millions of users and the person who reports the vulnerability gets...$5k. If I recall last week Mintlify wrote a blog post showcasing their impressive(ly complicated) caching architecture. Pretending…
I don't think anybody in SFBA-style software development, both pre- and post-LLM, is really resilient against these kinds of attacks. The problem isn't vibe coding so much as it is multiparty DLL-hell dependency stacks, which is something I attribute more to Javascript culture than to any recent advance in technology.
But like, this case isn't really a dependency or supply chain attack. It's just allowing remote code execution because, idk, the dev who implemented it didn't read the manual and see that MDX can execute arbitrary code or something. Or maybe they vibe coded it and saw it worked and didn't bother to check. Perhaps it's a supply-chain attack on Discord et al to use Mintlify, if thats what you meant then I apologize.
I think you're right that I have an extreme aversion to SFBA-style software development, and partly because of how gen-ai is used there.
Re: We pwned X, Vercel, Cursor, and Discord through a supply-chain attack
#64I struggle to understand the issue .. could someone help me out ? Ok, you got " https://discord.com/_mintlify/_static/hackerone-a00f3c6c/lma... " to send a controlled payload But regular users will never hit " https://discord.com/_mintlify/_static/hackerone-a00f3c6c/lma... ", so they will never execute your script I fail to understand how this can be exploited, by whom and in what conditions
You're pretty much on the money. Reflected XSS requires social engineering to really target anyone without other primitives. Unfortunately this report is not very clear about the tangible impacts or limitations of what they could do with this particular XSS either. Saying that every Mintlify customer was "vulnerable to account takeover with a single malicious link" strikes me as specious to say the least. Still, can'…
Re: We pwned X, Vercel, Cursor, and Discord through a supply-chain attack
#65I struggle to understand the issue .. could someone help me out ? Ok, you got " https://discord.com/_mintlify/_static/hackerone-a00f3c6c/lma... " to send a controlled payload But regular users will never hit " https://discord.com/_mintlify/_static/hackerone-a00f3c6c/lma... ", so they will never execute your script I fail to understand how this can be exploited, by whom and in what conditions
Apparently one of the other linked posts shows how you can also gain RCE, since the docs are statically pre-rendered and there’s no sandboxing to prevent you from evalling arbitrary JavaScript.
Re: We pwned X, Vercel, Cursor, and Discord through a supply-chain attack
#66The fact that SVG files can contain scripts was a bit of a mistake. On one hand, the animations and entire interactive demos and even games in a single SVG are cool. But on the other hand, it opens up a serious can of worms of security vulnerabilities. As a result, SVG files are often banned from various image upload tools, they do not unfurl previews, and so on. If you upload an SVG to discord, it just shows the raw…
If only there was a widely used vector format that had script support and also decades of work on maintaining a battle-tested security layer around it with regular updates on a faster release cycle than your browser. That'd be crazy. Sure would suck if we killed it because we didn't want to bother maintaining it anymore. (Yes I'm still salty about Flash.)
Re: We pwned X, Vercel, Cursor, and Discord through a supply-chain attack
#67Found by a 16 year old, what a legend.
Re: We pwned X, Vercel, Cursor, and Discord through a supply-chain attack
#68Re: We pwned X, Vercel, Cursor, and Discord through a supply-chain attack
#69ALSO as someone who maintains a file upload pipeline I run every SVG through a sanitizer... Tools like DOMPurify remove scripts and enforce a safe subset of the spec... I even go as far as rasterizing user uploaded vectors to PNG when possible
HOWEVER the bigger issue is mental... Most folks treat SVG like a dumb image when browsers treat it like executable content... Until the platform changes that expectation there will always be an attack surface
Re: We pwned X, Vercel, Cursor, and Discord through a supply-chain attack
#70Earlier quoted context omitted.
You're pretty much on the money. Reflected XSS requires social engineering to really target anyone without other primitives. Unfortunately this report is not very clear about the tangible impacts or limitations of what they could do with this particular XSS either. Saying that every Mintlify customer was "vulnerable to account takeover with a single malicious link" strikes me as specious to say the least. Still, can'…
imo, the impact is pretty clear here. an unsuspecting user clicks (or is redirected) to one of these malicious links on the platform (ex. vercel); the script grabs their cookie and credentials and sends it to the attacker. they now have full access to the victim's account.