You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An attacker can DoS (Denial-of-Service) a stream (and possibly the whole app) simply by exploiting an oembed bug. A GET request to the affected stream will become so slow to respond, rendering the PHP process handling that request busy for a long time, a few more GET requests and you can overwhelm the server.
What steps will reproduce the problem?
Just submit many [ ](oembed:https://www.youtube.com/) in a post message, using a hand crafted request because the rich text editor alters the text.
An attacker can DoS (Denial-of-Service) a stream (and possibly the whole app) simply by exploiting an oembed bug. A
GET
request to the affected stream will become so slow to respond, rendering the PHP process handling that request busy for a long time, a few moreGET
requests and you can overwhelm the server.What steps will reproduce the problem?
Just submit many
[ ](oembed:https://www.youtube.com/)
in a post message, using a hand crafted request because the rich text editor alters the text.I used cURL
Proof of concept
https://testoembedissue.humhub.com/s/welcome-space/
Additional info
The text was updated successfully, but these errors were encountered: