This article is within the scope of WikiProject Computer security, a collaborative effort to improve the coverage of computer security on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.Computer securityWikipedia:WikiProject Computer securityTemplate:WikiProject Computer securityComputer security
This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing
Should add something about PHP injection being a form of arbitrary code execution but that the term arbitrary code execution is not commonly used for higher level arbitrary command execution bugs.SkyLined (talk) 23:49, 6 March 2008 (UTC)[reply]
Just ran into a situation where someone assumed that all exploits that allow for Arbitrary (or "Remote", which Wikipedia cross references to here) Code Execution, means that a "hacker" that executes code on a hacked machine somehow, magically gains full control of the whole computer. This situation started from a new exploit discovered on HP Printers. My sense is that "full control" is not always the end-result of code being executed remotely. Read the article and it seems to confirm this, but I think that for the general public, the article would be improved if it spelled out explicitly the varying levels of "control" that can be achieved by executing code remotely, and give some real-life examples of these. I assume that in some cases the level of "control" is highly limited, which in others total access can be achieved. It would be good if this article spelled this out clearly so that there is no doubt that merely executing code does not necessarily mean total control.2605:6000:6947:AB00:1D9B:AE9C:E37E:9175 (talk) 20:03, 7 August 2018 (UTC)[reply]