Do the math: How we took over ChatGPT accounts (parameter.ai)

329 points by armcat a day ago

yellow_lead 21 hours ago

> 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.

Catloafdev 16 hours ago

A bounty like this is a polite "thanks asshole, fuck off, don't do it again" rate.

Paying effectively nothing for vulnerabilities just means they don't want to deal with the program.

Wild to think a company supposedly worth a $trillion+ is doing shit like this.

Forgeties79 14 hours ago

Because they shouldn’t be worth that tbh. They are a cash burning operation hoping to get what they can before the music stops.

andai 5 hours ago

fsckboy 14 hours ago

A company worth trillions does not have trillions, that is the expectation for what it will be worth in the future based on money it has already spent and will need to keep spending.

Moreover, that translates to "it's actually carrying a huge nut* that puts extremely intense pressure on the company to figure out how to make as much money as possible as soon as possible."

(*nut is a slang word from loan sharking that has been adopted by (personal et al) finance people. It means "how much do you owe each month?" in the sense of, if you want to do a startup, advisors could ask, "what's your nut, and how much do you have left to self-invest?" Because monthly expense can be combined to a lump sum, it can also mean the size of the overall loan where the monthly interest is called the vig, "as long youze got da nut, you owe me da vig;" from vigorish, which would also require an etymology, but I'm assuming it's the word vigor combined with licorice meaning bitter tasting medicine, and nut because squirrels busy themselves carrying nuts.)

----

and if we can... and remember flame-prone people, if you reject the "can" premise, then the rest of the argument goes away, and you don't need to dispute it, you just say "you can't nuff said"; people here frequently seem challenged by propositions.

so, if we can...loosely describe the attitude you show here toward high market cap companies to be compatible with "left" or "socialist" or "populist" views shared by many others here, then I'll point out that at the same time wanting higher market prices paid for bounties because 'sploits are so expensive, is actually advocating for the same dread capitalist market based solution that leads to trillion dollar companies that never even had a trillion to begin with.

ibaikov 17 hours ago

I took over user accounts in Microsoft Copilot (there are caveats but still), and they asked me to provide additional information of the exploit (they wanted a video) and before I sent it they fixed the vulnerability, didn't pay me a cent. Fair? Idk.

pvtmert 17 hours ago

Typical $MSFT behavior, I can see why NightmareEclipse (ie. YellowKey zero-day exploit) got released without prior fix.

zeroq 9 hours ago

It's a complicated issue in current LLM world where every day is a zero day, but fuck me sideways, company that claims to be worth trillion of dollars paying 5k for such an exploit is insulting at best.

It's been years since I hanged out with wizards selling such exploits like trading cards, but I bet there are still tons of brokers that will be more than happy to wire you legal money for such finding.

I mean, kudos for the team for doing the right thing. It's great PR and another big one in the portfolio, but, as other have said already, I doubt the next group will even bother contacting OpenAI.

dgellow 19 hours ago

That’s so low. That’s the level of bounty I awarded researchers when I was managing the bug bounty program at a small startup, it’s just ridiculous coming from a large company like OpenAI

amelius 18 hours ago

But on the other hand, you can use AI now to find those vulnerabilities.

tescreal 18 hours ago

baxtr 18 hours ago

dgellow 17 hours ago

windexh8er 19 hours ago

I find Sam Altman recent comments very "low" as well, neither matters. So in that case I think bounty hunters should just cold shoulder idiocracy and sell these to the underground. Let their customers be abused and complain about how OAI isn't protecting them. Each one of these types of events could cost them thousands of dollars in lost revenue and/or internal support.

rootnod3 16 hours ago

2 trillion $ companies should have the money to pay for these exploits. If they don’t, go tucking exploit them. If they don’t give a fuck about stealing knowledge from copyrighted material and private git repos, light em up.

throwaway98797 18 hours ago

some people don’t want to be criminals as a matter of ethics

but hey you do you

odyssey7 18 hours ago

tonyedgecombe 18 hours ago

Black616Angel 18 hours ago

blurbleblurble 17 hours ago

windexh8er 15 hours ago

oth001 17 hours ago

dist-epoch 21 hours ago

This is a pet peeve of tptacek:

> server-side vulnerabilities are worth very little, because they quickly get patched.

dannyw 20 hours ago

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.

throwaw12 19 hours ago

then server side vulnerabilities should not be reported, instead sell the data, more profitable

petcat 19 hours ago

tomjen3 2 hours ago

hashstring 8 hours ago

Technically this is what you’d call a client-side vuln, but yes, server-side as in cloud.

thatsabadlook 20 hours ago

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.

varispeed 19 hours ago

Should be given $5-10million under NDA. No headlines.

layer8 19 hours ago

weird-eye-issue 19 hours ago

goodmythical 18 hours ago

kamban 18 hours ago

They have just announced free API credits for Pro plan users up to $500 per month. Irony.

zxilly 15 hours ago

To be fair, based on the profit margins indicated in DeepSeek’s reports, a $500 API credit might only cost them $5 to provide.

alfiedotwtf 9 hours ago

The buyer of your second vulnerability all depends on how you’re treated for your first vulnerability

jryle70 19 hours ago

OpenAI acknowledging and fixing the bug is worth millions

yeahsure 17 hours ago

Yeah... idk, sounds like when I was starting out almost 30 years ago my clients constantly lowballed me saying "but think of the exposition! this project will give you" lol

jryle70 17 hours ago

varispeed 19 hours ago

Indeed, it's like "here peasant, have this fortune of $5,000, may it change your life". Pathetic.

siva7 19 hours ago

that wouldn't be the time worth of many people here to make the security report for OAI..

cowlevel 13 hours ago

lxgr 21 hours ago

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

randomblock1 9 hours ago

On the Work environment selector, "in the cloud" says "available on any device and can access your computer". Which seems pretty clear to me. (not that the labeling makes the security issue any better)

albert_e 18 hours ago

Claude Code terminal has "remote control" option activated via /rc command. -- somewhat similar in that it still runs the session on the PC/Mac but allows the Claude authenticated user to access the session via internet / app

I am guessing this ChatGPT functionality is a similar Codex feature?

But this session is disconnected when the conversation is /exit ed

lxgr 13 hours ago

Sounds similar, but the problem is exactly that I don’t think there’s any way to disconnect such a session, nor to even see that it is connected to my computer in the first place. There’s a small notice when initially starting it on the mac, that’s it.

dumberquestions a day ago

Does no one write their own blogs anymore?

zahlman an hour ago

I write mine, and will continue to do so, by hand. I would never consider letting an LLM touch my writing.

Posting frequency is another matter…

trungto 18 hours ago

For my personal blog [0], I am still writing without LLM assistance. The goal is to test how well I understand the topic I am writing about, as well as to improve my own writing.

[0] https://trung.to

armcat 19 hours ago

I actually still write my own blog [1] :sweat_smile:

Pure html by hand, using vim. No frameworks, no nothing, single stylesheet. I think there are a few others around here that still do this.

[1] https://armincat.com/

bookofjoe 18 hours ago

lifeisloving 21 hours ago

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.

zx8080 21 hours ago

For who?

loveparade 21 hours ago

For the LLMs so they get new training data

zahlman 14 hours ago

Something about the writing style here makes it hard for me to follow what actually happened. The section about JSONP for example seems to be explaining how JSONP works and how it's designed as an attempt to work around these attacks, but that explanation is then passed off as an explanation of how they bypassed the protection. And the whole premise seems to be about how manipulating the Preview content let them work through multiple defensive layers, but I don't see an explanation of how they directly controlled that content in the first place. I would have thought that the only control you have over the content of "an ordinary public ChatGPT share" is the prompt text, and that any migration of that text into "a small working webpage using its Preview feature" is up to the model deciding to generate that "HTML block" in response.

0c3ca83 13 hours ago

They're writing for bots, not humans. This is a marketing piece. They're trying to get themselves to come up as the answer when people ask chatbots questions.

You're not the target audience of writing on the Internet anymore.

cowlevel 13 hours ago

It's AI written so of course it's hard to follow.

morgaesis 11 hours ago

Your conclusion does not follow from your premise.

mediaman 10 hours ago

krackers 9 hours ago

It's surprising that using JSONP in this way is even allowed. At one point google explicitly made sure to prevent this flavor of attack

https://stackoverflow.com/questions/2669690/why-does-google-...

kenmacd 7 hours ago

hnslop (using salahadawi, using Pangram) puts this at 100% AI written, so that's probably why.

Report: https://www.salahadawi.com/hacker-news-ai-detector/50314699

hnslop: https://hnslop.nilsherzig.com/

zahlman 2 hours ago

Oh, I don't doubt that. But most of the time I can pick out useful information from the claudeslop. This piece seems almost deliberately obscurantist.

Kuyawa 18 hours ago

$5000 is a joke. They pay millions to their top devs and still have more holes than a colander so a nice guy shows you a huge opening in your platform and all you can give him is a pat on the shoulder? Did you fire your top devs and hire that guy for a million bucks plus options? Did you sue the security firm you paid millions to audit the issues?

I really hope they get hacked and crash down burning in flames like the Hindenburg

cbsks 18 hours ago

I wonder if the new economics of finding bugs means that they pay the amount they think the tokens cost to find it.

aprilthird2021 14 hours ago

Makes negative sense. If it were that easy, OpenAI wouldn't have any bugs bc they could just run agents to exploit their own stuff and then fix all their bugs.

This bug could not be found by just asking an AI "find bugs in ChatGPT", that's why it was reported through a bug bounty programs and that's why it should be worth more than $5k

stavros 16 hours ago

Over the probability that you'll find something.

tsunamifury 18 hours ago

I think you know that the mentality of a company like this is “security is a risk but not a reward and whoever captures the reward kills everyone else”

usernametaken29 21 hours ago

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.

torben-friis 21 hours ago

Did you mean exponentially? Logarithmic increase doesn't sound too bad.

dahart 19 hours ago

I’m sure exponential is what parent meant, but geometric (edit: polynomial) is what actually happens, not exponential. Code complexity increases linearly when it doesn’t interact with other features, and geometrically when it does. In the worst case, complexity increases as the square of lines of code. That is still very, very bad, but it’s not exponential.

ebertucc 18 hours ago

codechicago277 18 hours ago

Pannoniae 21 hours ago

it's not like microservices fare better, when you introduce them, you've traded a hard problem for a hard problem and distributed computing...

wg0 21 hours ago

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.

rglover 19 hours ago

I like LOEC: Lines of Effective Code.

Much easier to reason and make decisions if the bar is "yeah it exists, but is it effective relative to its intended purpose?" This weeds out buggy code as well as under performant code. If it's not effective (broken, too slow, etc), it either needs a refactor or thrown on the scrap pile.

elendilm 21 hours ago

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.

someothherguyy 20 hours ago

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.

cowlevel 12 hours ago

brazukadev 20 hours ago

pessimizer 17 hours ago

> Now what about those millions of lines of code? Wasn’t the agent swarm supposed to take care of it?

What's the joke? They're literally saying, every day, that this is true to a civilization endangering extent. They're making demands based on this, and politicians are taking up those demands.

And now they're paying bullshit $5K bug bounties for account-stealing exploits on their own platform. They should have paid more just the make the bug seem more grandiose; I don't know who let them get away with this - this is what happens when CEOs run their own PR I guess. It's basically an public announcement that they're total fakes.

6thbit 20 hours ago

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.

hridyaagrawal 14 hours ago

$5000 is a joke for a "P1" vuln

itsafarqueue 14 hours ago

My theory is vulns will never pay out big especially now, no matter how serious. Imagine they paid out $50k+ — it’d spawn an industry doing nothing but.

verteu 13 hours ago

For a company that truly cares about secure software, that seems like an ideal outcome.

htk 15 hours ago

5k makes me think the next guy is gonna sell his exploit in the black market instead.

15o9o a day ago

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?

qup 20 hours ago

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.

latexr 19 hours ago

> I'm trying not to have any important data to even lose

This is the way. Respect user privacy and keep as little data as possible, and not only do you become a less attractive target, if you are targeted the outcome won’t be so bad.

dataviz1000 21 hours ago

> please don’t login as me

Please don't drain my $6.5 billion in Dogecoin.

chamomeal 20 hours ago

Been sayin this for years. Everybody in the world world: just BE COOL. Solves like every internet problem at once.

15o9o 19 hours ago

we all joke but spiritual communities have been saying this is the way for years. Like the law of one stuff.

atrokhymchuk 21 hours ago

if only they had some sort of cybersecurity state of the art thing...

jwpapi 18 hours ago

I think there was another HN discussion about it re bounty value and as far as I remember the issue is not that big companies are greedy in that case, but rather that over time it’s strategically better to have lower bounties so less people are interested in it.

5 or 50k doesnt matter to them. And this bug in terms of severity is very high imho.

aprilthird2021 14 hours ago

But couldn't they just turn around and sell this hackers for much more money?

monster_truck 20 hours ago

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)

joshuamoyers 13 hours ago

unrelated to this, but this company randomly reached out disclosing a vulnerability to us (test environment, synthetic tenant). on the one hand, thank you, it’s patched. on the other - we do not have a bug bounty program and this is not welcome. having agent swarms randomly breaking in to environments and then marketing their services in the disclosure is not an ideal sales tactic, in addition to being illegal.

uniq7 13 hours ago

I don't want to defend them, but the alternative is that they do nothing and you don't know about the vulnerability until a bad actor exploits it (something easy and cheap nowadays).

I'm confused, would you welcome that more?

pamcake 9 hours ago

False dichotomy. There are plenty of other possible approaches outside of "having agent swarms randomly breaking in to environments and then marketing their services in the disclosure" and "do nothing".

uniq7 6 hours ago

pllbnk 15 hours ago

It's exhilarating (for the lack of the knowledge of a better word) to see OpenAI and Anthropic starting getting hacked and getting a taste of their own medicine. Brings back hope that actual software engineering is not dead yet.

jareklupinski a day ago

> 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

kro 21 hours ago

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.

weird-eye-issue 19 hours ago

> 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.

This has been a thing since forever lol

dpark 19 hours ago

Security software fetching links will not trigger this behavior. It needs to be done in the context of the actual ChatGPT user so that a JavaScript payload can run.

If merely GET on the link was sufficient to trigger the behaviors, the adversary generating the link would just GET it themselves.

kro 18 hours ago

TobTobXX 21 hours ago

... 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...

Antipode 20 hours ago

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.

extraextra 19 hours ago

God I hate those

dist-epoch 21 hours ago

I wanted to check your website from your profile, but then I remembered your advice. Thanks!, dodged a potential bullet

bossyTeacher a day ago

Also many emails from tech companies today:

- "sign in via one-time code."

- "Click here to see our latest update".

jareklupinski 21 hours ago

dont click links

250k refresher fee

pkthunder 20 hours ago

atrokhymchuk 21 hours ago

kotaKat 21 hours ago

"Scan this QR code!"

Razengan 21 hours ago

Thanks! Here, click on this link to get paid

jiveturkey 13 hours ago

Hex aka Parameter is an irresponsible company, on my blacklist. after they did an unsolicited pentest on us, we scheduled a call. joke of a team.

hilarious that their headline message, on every web page, is `Backed by YC`.

also, the product is way behind their competitors anyway.

really cool exploit they found here, but that doesn't make them a company worth doing business with.

Zeruxe 16 hours ago

5k is nothing for the amount of headache you just saved them..

j9feng 18 hours ago

Claude or Gemini didn’t find the vulnerability on ChatGPT?

Yieldz 17 hours ago

Sigh. With how good Openai are good in programming frontier agents, they still have weak security. Hmmn, i'm short of words.

nickphx 19 hours ago

why didnt the black box of bullshit company detect this? for a group that touts every inane 'discovery' with hyperbolic bullshit, they really fall short on delivering anything of actual value, just rehashed bullshit.

marwaneet 21 hours ago

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.

brabel 20 hours ago

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??

steve1977 21 hours ago

Production scale is not production grade I guess...