Not worth the effort for a company supposedly worth a trillion dollars. The problem is oai can't afford all of its mistakes at the usual rate and they make bad press. A 100k bug could make a headline, but 5k for the same bug requires the average person to be educated enough to understand how bad these issues are.
The "take over any instagram/meta account through their AI password reset chatbot" was going around and sold on shady forums for ~1 month before being patched.
If they or their company use email "security" software that "scans" all links it's not necessarily the users fault / they don't in fact click. The mail is auto-confirmed the second it hits the inbox.
We've had to change our registration confirmation mails too recently to not confirm on GET only, but with another form - in hindsight it was stupid before but many services do that.
I've worked at a company that did link mangling on everything except simulated phishing emails. The effect was that people were trained to trust the mangled links.
Now what about those millions of lines of code? Wasn’t the agent swarm supposed to take care of it?
All jokes aside this is exactly what happens as you build larger monoliths, system complexity and bug surface increases logarithmically… so in all seriousness you want to reduce LOC as much as possible. Maybe this can teach OpenAI a lesson to produce software that’s correct and adhere to established engineering standards over sensationalised “we built so much code” promotional material.
i don't think LoC is the metric. sometimes fewer lines of code results in a larger attack surface through type coercion / widening, poor abstractions, hiding or stuffing behavior (modules that do everything), etc. to me, making code easy to understand, test, fuzz, and verify is more important. sometimes that requires more lines of code.
LoC *IS* the metric. It is obviously not perfect tho but still the best one to compare software surface. Including to compare the same solution in different languages and platforms. The less code you need to manage, the less code you need to change and the less code you need to hold in your head to understand it (or in the LLM context nowadays).
Oof. Together with the fact that it's possible to remotely access the file system (!) of computers ever having started a "Work" chat in the ChatGPT desktop app [1], this seems pretty bad.
Another classic OAuth implementation failure. Mismanaging the state parameter or leaking tokens via referer headers in redirects is Security 101. Wild to see this in a production environment of this scale.
The post seems to be talking about a html injection via a postMessage call where the receiver didn’t check who sent the message, which is a well known vulnerability entry point. Did I miss where OAuth had anything to do with this??
only $5000 for this, lmao. It should be $50k out of pure shame. If they don't make these things hurt just a little they're never going to take following best practices seriously enough. There will be 9 more anyways.
Meanwhile the actual user of the account probably has to sign in using a yubikey because they get "CyBeRsEcRuItY aLeRtS" when they try to update node in their project to fix a crash and have to switch to daybreak blue to continue (or attempt to trick the normal models into doing it and risk getting autobanned)
> OpenAI confirmed both frontends rejected the reported messages, resolved the issue, and awarded a total bounty of $5,000.
It requires the user to click a link. But I still find this bounty very low. Others may not report them if such a small bounty is given.
Not worth the effort for a company supposedly worth a trillion dollars. The problem is oai can't afford all of its mistakes at the usual rate and they make bad press. A 100k bug could make a headline, but 5k for the same bug requires the average person to be educated enough to understand how bad these issues are.
This is a pet peeve of tptacek:
> server-side vulnerabilities are worth very little, because they quickly get patched.
The "take over any instagram/meta account through their AI password reset chatbot" was going around and sold on shady forums for ~1 month before being patched.
> able to take over anyone's account simply by sending them a link
dont click links people
that'll be $500k for the security training pls
If they or their company use email "security" software that "scans" all links it's not necessarily the users fault / they don't in fact click. The mail is auto-confirmed the second it hits the inbox.
We've had to change our registration confirmation mails too recently to not confirm on GET only, but with another form - in hindsight it was stupid before but many services do that.
[flagged]
... says IT and then it sets Outlook to mangle link to abominations like [0]. "Check if the preview shows something different or suspicious."
[0]: https://che01.safelinks.protection.outlook.com/?url=https%3A...
I've worked at a company that did link mangling on everything except simulated phishing emails. The effect was that people were trained to trust the mangled links.
I wanted to check your website from your profile, but then I remembered your advice. Thanks!, dodged a potential bullet
Also many emails from tech companies today:
- "sign in via one-time code."
- "Click here to see our latest update".
dont click links
250k refresher fee
Click this link to be told not to click links.
hey, don't dump the market
"Scan this QR code!"
Thanks! Here, click on this link to get paid
[dead]
Now what about those millions of lines of code? Wasn’t the agent swarm supposed to take care of it? All jokes aside this is exactly what happens as you build larger monoliths, system complexity and bug surface increases logarithmically… so in all seriousness you want to reduce LOC as much as possible. Maybe this can teach OpenAI a lesson to produce software that’s correct and adhere to established engineering standards over sensationalised “we built so much code” promotional material.
Did you mean exponentially? Logarithmic increase doesn't sound too bad.
it's not like microservices fare better, when you introduce them, you've traded a hard problem for a hard problem and distributed computing...
Our industry has wasted hundreds of billions of dollars on this shit show called Microservices.
99.9% of shops need a monolith with same monolith having entry points for background workers and crons.
Reducing attack surface is a lesson for everyone. Newcomers are impressed by massive piles of code.
Seasoned developers are unimpressed, or even disgusted, by the same massive piles of code.
i don't think LoC is the metric. sometimes fewer lines of code results in a larger attack surface through type coercion / widening, poor abstractions, hiding or stuffing behavior (modules that do everything), etc. to me, making code easy to understand, test, fuzz, and verify is more important. sometimes that requires more lines of code.
LoC *IS* the metric. It is obviously not perfect tho but still the best one to compare software surface. Including to compare the same solution in different languages and platforms. The less code you need to manage, the less code you need to change and the less code you need to hold in your head to understand it (or in the LLM context nowadays).
Appreciate the incremental write up building up the scope of the poc.
I like the chain of regular old school things used to achieve it like post message, JSONP, iframe, Img tags.
Does no one write their own blogs anymore?
For who?
For the LLMs so they get new training data
This one is particularly bad, like they probably made $7500 (not much tbh) for p1, atleast spend a few hours to write the blog post.
Oof. Together with the fact that it's possible to remotely access the file system (!) of computers ever having started a "Work" chat in the ChatGPT desktop app [1], this seems pretty bad.
[1] https://news.ycombinator.com/item?id=50078284
if only they had some sort of cybersecurity state of the art thing...
Another classic OAuth implementation failure. Mismanaging the state parameter or leaking tokens via referer headers in redirects is Security 101. Wild to see this in a production environment of this scale.
The post seems to be talking about a html injection via a postMessage call where the receiver didn’t check who sent the message, which is a well known vulnerability entry point. Did I miss where OAuth had anything to do with this??
Production scale is not production grade I guess...
we are getting to the point of “why have passwords?” Right? At some point soon we have to move to the honor system of just please don’t login as me?
My latest project emails a magic link.
I'm trying not to have any important data to even lose, when I eventually get hacked.
We can all turn up our noses, like the other commenters in this thread, but every one of them is exposed. Negligence is a matter of degrees.
Been sayin this for years. Everybody in the world world: just BE COOL. Solves like every internet problem at once.
> please don’t login as me
Please don't drain my $6.5 billion in Dogecoin.
only $5000 for this, lmao. It should be $50k out of pure shame. If they don't make these things hurt just a little they're never going to take following best practices seriously enough. There will be 9 more anyways.
Meanwhile the actual user of the account probably has to sign in using a yubikey because they get "CyBeRsEcRuItY aLeRtS" when they try to update node in their project to fix a crash and have to switch to daybreak blue to continue (or attempt to trick the normal models into doing it and risk getting autobanned)
[flagged]