4 ms·
What makes you say that? SSH, RDP, even hitting a web service are all valid cases of authorized remote code execution. It's not the remote or execution parts
by kevindamm 3y ago
What makes you say that? SSH, RDP, even hitting a web service are all valid cases of authorized remote code execution. It's not the remote or execution parts that are bad.
- dist-epoch 3y agoNow you're redefining words. Remote code execution means a single thing, running JavaScript when accessing a web page and using SSH as intended is not RCE. https://en.wikipedia.org/wiki/Remote_code_execution https://en.wikipedia.org/wiki/Remote_code_execution https://www.google.com/search?q=Remote+code+execution https://www.google.com/search?q=Remote+code+execution
- kevindamm 3y agoI may not have been clear -- I agree that RCE, unqualified, means unauthorized RCE. but then you said there was no such thing as an "authorized" RCE and that's where I beg to differ. Sure, the term isn't used much but it wasn't the clarifying point I wanted to make above, that there is a difference between authenticated and authorized. The links you point to there are about "RCE attack" which also implies not authorized.
- dist-epoch 3y agoYour original post: > in the introductory paragraph it reads "unauthenticated, targeted remote code execution ... I believe this means it was unauthorized, not unauthenticated. You again: > agree that RCE, unqualified, means unauthorized RCE So you agree that your "unauthorized" qualification from your orignal post was unwarranted, since all unqualified RCE are unauthorized. Now if you want to split hairs, you'll say "but the introductory paragraph said unauthenticated, which is qualified RCE, thus I am still right". ok then