Remote Code Execution
Also called RCE.
Running attacker code on a target over a network.
What it is
A vulnerability impact in which an attacker can execute arbitrary code on a target system from across a network, without local access. It is typically the most severe outcome a remote flaw can produce.
Why it matters
RCE provides an initial foothold and is the highest-priority class to patch and detect. In IR, confirming RCE versus a lesser impact drives the urgency and scope of response.
In practice
A crafted request to an internet-facing application triggers a deserialization bug that runs operating-system commands on the host.
What to look for
- Exposed services with critical RCE advisories.
- Web or service processes spawning shells.
- Scanning activity aimed at the vulnerable path.
Common mistake
Patching only internet facing hosts. Internal hosts fall right after the first foothold.
Practice it nearby
CyberKit has no tool for this term itself. These are the closest places to practice it.
- Risk Scoring
Score a vulnerability with CVSS v3.1, or an incident across five dimensions, and see the reasoning behind each number.
- Map and Score
Map real procedures to ATT&CK techniques, then pick the CVSS v3.1 metrics for real vulnerabilities.
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
Nessus Commercial
A vulnerability scanner that checks hosts for known flaws and missing patches.
-
Qualys VMDR Commercial
A cloud platform that scans assets and ranks vulnerabilities for patching.
-
OpenVAS Open source
An open source vulnerability scanner with a large set of checks.
-
Nuclei Open source
Runs community templates that test for specific, newly published flaws.
Read next
- Local Privilege Escalation: Gaining higher privileges from an existing local foothold.
- Exploit Chain: Linking multiple bugs together to reach a final objective.
- Shellcode: Compact, self-contained machine code that runs from an injected buffer.