Talk:Arbitrary code execution

Computer Security: Computing High‑importance

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 articles

High

This article has been rated as High-importance on the project's importance scale.

This article is supported by WikiProject Computing (assessed as High-importance).

Things you can help WikiProject Computer Security with:

Article alerts will be generated shortly by AAlertBot. Please allow some days for processing. More information...

Review importance and quality of existing articles
Identify categories related to Computer Security
Tag related articles
Identify articles for creation (see also: Article requests)
Identify articles for improvement
Create the Project Navigation Box including lists of adopted articles, requested articles, reviewed articles, etc.
Find editors who have shown interest in this subject and ask them to take a look here.

Computing

	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 articles
???	This article has not yet received a rating on the project's importance scale.

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]

SonicWALL

Come on now! Stop posting this page as a reference in every single signature. TekBoi [Ali Kilinc] (talk) 17:41, 30 March 2016 (UTC)[reply]

Extent and Limits of "Arbitrary Code Execution"

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]

I've fleshed this out a little bit, but I think that it could still be improved significantly Samlanning (talk) 18:34, 11 May 2019 (UTC)[reply]

Use of "Attacker"

There is a line in the beginning of the article saying "In computer security, arbitrary code execution (ACE) is an attacker's ability to run any commands or code of the attacker's choice on a target machine or in a target process." Despite the fact that ACE isn't only an ability for attackers, but has multiple applications, some of which aren't malicious. What should be done about this? -A Fluffy Kitteh (FluffyKittehz User Profile Page) 20:35, 27 January 2022 (UTC)[reply]

An Attack is a fairly standard term for the exploitation of faults in a system that causes it to behave outside its intended bounds. I can't really point to any particular reading on it but you'll see folks like those from AGDQ using similar lingo in their own write-ups. In the Information Security context it carries more of a Game Theory connotation of "Attack/Defend". RequestSelector (talk) 19:13, 1 June 2023 (UTC)[reply]