orkj
Joined 13 years ago
Joined 13 years ago
However, if I am reading this correctly, your PoC falls in the category described here: https://react2shell.com/
> Anything that requires the developer to have explicitly exposed dangerous functionality to the client is not a valid PoC. Common examples we've seen in supposed "PoCs" are vm#runInThisContext, child_process#exec, and fs#writeFile.
> This would only be exploitable if you had consciously chosen to let clients invoke these, which would be dangerous no matter what. The genuine vulnerability does not have this constraint. In Next.js, the list of server functions is managed for you, and does not contain these.
Context: This is from Lachlan Davidson, the reporter of the vulnerability
They are probably referring to the text in the basic auth "pop-up" which is usually set like
WWW-Authenticate: Basic realm="my text"
Not sure if that was the missing case for you, but just in case someone reads this and gets the same feeling as me
The word "bad" is also used several times, and can be argued is also useful to put in the title
Granted it's far from as smart as pebble, but that battery life... ♥
https://boehs.org/node/everything-i-know-about-the-xz-backdo...
IRC activity