←back to thread

646 points blendergeek | 1 comments | | HN request time: 0.37s | source
Show context
bflesch ◴[] No.42726827[source]
Haha, this would be an amazing way to test the ChatGPT crawler reflective DDOS vulnerability [1] I published last week.

Basically a single HTTP Request to ChatGPT API can trigger 5000 HTTP requests by ChatGPT crawler to a website.

The vulnerability is/was thoroughly ignored by OpenAI/Microsoft/BugCrowd but I really wonder what would happen when ChatGPT crawler interacts with this tarpit several times per second. As ChatGPT crawler is using various Azure IP ranges I actually think the tarpit would crash first.

The vulnerability reporting experience with OpenAI / BugCrowd was really horrific. It's always difficult to get attention for DOS/DDOS vulnerabilities and companies always act like they are not a problem. But if their system goes dark and the CEO calls then suddenly they accept it as a security vulnerability.

I spent a week trying to reach OpenAI/Microsoft to get this fixed, but I gave up and just published the writeup.

I don't recommend you to exploit this vulnerability due to legal reasons.

[1] https://github.com/bf/security-advisories/blob/main/2025-01-...

replies(8): >>42727288 #>>42727356 #>>42727528 #>>42727530 #>>42733203 #>>42733949 #>>42738239 #>>42742714 #
hassleblad23 ◴[] No.42727528[source]
I am not surprised that OpenAI is not interested if fixing this.
replies(2): >>42727750 #>>42730584 #
bflesch ◴[] No.42727750[source]
Their security.txt email address replies and asks you to go on BugCrowd. BugCrowd staff is unwilling (or too incompetent) to run a bash curl command to reproduce the issue, while also refusing to forward it to OpenAI.

The support@openai.com waits an hour before answering with ChatGPT answer.

Issues raised on GitHub directly towards their engineers were not answered.

Also Microsoft CERT & Azure security team do not reply or care respond to such things (maybe due to lack of demonstrated impact).

replies(2): >>42729126 #>>42734923 #
permo-w ◴[] No.42729126[source]
why try this hard for a private company that doesn't employ you?
replies(8): >>42729394 #>>42730264 #>>42730800 #>>42731345 #>>42732640 #>>42735360 #>>42736114 #>>42738383 #
bflesch ◴[] No.42731345[source]
Ego, curiosity, potential bug bounty & this was a low hanging fruit: I was just watching API request in Devtools while using ChatGPT. It took 10 minutes to spot it, and a week of trying to reach a human being. Iterating on the proof-of-concept code to increase potency is also a nice hobby.

These kinds of vulnerabilities give you good idea if there could be more to find, and if their bug bounty program actually is worth interacting with.

With this code smell I'm confident there's much more to find, and for a Microsoft company they're apparently not leveraging any of their security experts to monitor their traffic.

replies(1): >>42731656 #
orf ◴[] No.42731656[source]
Make it reflective, reflect it back onto an OpenAI API route.
replies(2): >>42735055 #>>42741643 #
1. bflesch ◴[] No.42741643[source]
I'm not a malicious actor and wouldn't want to interrupt their business, so that's a no-go.

On a technical level, the crawler followed HTTP redirects and had no per-domain rate limiting, so it might have been possible. Now the API seems to have been deactivated.