Remote Code Execution (RCE)

Remote code execution (RCE) describes a flaw that allows someone to run code of their choosing on another machine across a network, without having physical or prior legitimate access. It is among the most severe categories of vulnerability.

Why it matters

Running code means running with the privileges of the vulnerable program. That can enable data theft, installing persistent access or moving to other systems. Because such flaws in internet-facing software can be exploited at scale, they usually get high severity scores, and vendors issue urgent patches. Causes include unsafe deserialization, command injection, memory errors and flawed template or upload handling.

Example

A vendor announces a critical advisory for a widely used web framework and releases a fixed version. An administrator checks the inventory, finds three affected servers, applies the update within the planned emergency window and reviews logs for suspicious requests made before patching.

Common mistakes

• Delaying patches on internet-facing systems because no attack has been seen yet.
• Not knowing which software and versions are deployed, so exposure cannot be assessed.
• Running services as administrator, which increases the impact of a successful exploit.
• Passing user input to shell commands or evaluators.

Related

• Patch management
• CVSS
• Zero-day
• Vulnerability

This page is general information written by our editorial team and updated when documentation changes. Servers and providers differ, so test changes safely first. See our editorial policy and disclaimer.