upvote
it does not make sense to say RCE for something that does not have an open port on the system
reply
If someone opens an encrypted email that came from an attacker using GnuPG and code is executed on his machine as a result, that is still remote code execution.
reply
What is not "remote" code execution under this definition?
reply
Have you ever heard of IP over Avian Carrier? It might help expand your definition of “remote”.

In all seriousness, “remote” in this case means attacker controlled.

reply
Are you suggesting the existence of exploits outside of the definition of "attacker controlled"?

If not, and all exploits are attacker controlled, it sounds like all exploits are RCE.

EDIT I guess I have to weaken the last condition since we haven't proved all exploits are "code execution", but we have at least proved all exploits are "remote".

reply
It makes sense to assume the worst, then try to achieve it. And only if you achieve it so you tag it as such. You can't announce vulnerabilities to the world based on vibes of what it might do....

"Yeah this is a classic double free. We can't think of a way to transform it into a RCE or something like that, we've also failed at having LLMs do it so far. but in the current climate it could happen so we humbly ask the tag of most dangerous vulnerability please. Not just this disclaimer. We want 9.9 CVE that says RCE!!"

This is ridiculous.

reply