sast-rce

Map user-controlled data to dangerous sinks and write RCE findings to rce-results.md.

1.3k|61|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/utkusen/sast-skills --skill sast-rce
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sast-rce
Source: https://github.com/utkusen/sast-skills/tree/main/sast-files/.agents/skills/sast-rce
Command: npx skills add https://github.com/utkusen/sast-skills --skill sast-rce

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly identify and prioritize Remote Code Execution vulnerabilities in a codebase by mapping dangerous sinks to tainted inputs and producing a structured risk report.

Core Features & Use Cases

  • Three-phase workflow: recon, batched verify, and merge to locate, validate, and consolidate RCE findings.
  • Handles OS command execution sinks, eval-like code execution, and unsafe deserialization patterns across languages.
  • Use case: assess a codebase with user input flows to generate a comprehensive RCE risk report (sast/rce-results.md).

Quick Start

Run the RCE assessment on your project to generate a sink map and consolidated findings.

Frequently Asked Questions about sast-rce

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify remote code execution vulnerabilities in my codebase?

To identify remote code execution vulnerabilities, you can run an assessment that maps dangerous sinks to tainted user inputs. This process traces user-controlled data through the codebase to validate taint paths and generates a consolidated risk report.

How does taint tracking detect unsafe sinks for code execution?

Taint tracking detects unsafe sinks by mapping how user-controlled data propagates through the application to dangerous endpoints. It validates these data flows to confirm if malicious input can reach OS command execution, eval functions, or unsafe deserialization patterns.

How do I triage RCE risks across a large software project?

You can triage RCE risks across a project using a three-phase workflow: recon to locate sinks, batched verify to validate taint paths, and merge to consolidate findings. This produces a structured rce-results.md report for remediation.

Do I need an architecture file to scan for RCE vulnerabilities?

Yes, you need a sast/architecture.md file to exist before scanning for RCE vulnerabilities. The analysis uses this architecture context to understand the codebase structure and writes the final consolidated findings to sast/rce-results.md.

What types of dangerous sinks are covered by RCE security assessments?

RCE security assessments cover several dangerous sink types including OS command execution, eval-like dynamic code execution, and unsafe deserialization patterns. These sinks are targeted across multiple programming languages to map potential exploit paths.

Why should I use a batched verify approach for taint tracking?

Using a batched verify approach for taint tracking isolates and validates specific data flow paths to reduce false positives. It confirms that untrusted input actually reaches dangerous sinks before merging results into the final risk report.