wrdn-code-execution

Detect server-side code-execution vulnerabilities by tracking source-to-sink paths across languages.

6|1|Updated Nov 23, 2023
One-click install
npx skills add https://github.com/gmcabrita/dotfiles --skill wrdn-code-execution-gmcabrita
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wrdn-code-execution
Source: https://github.com/gmcabrita/dotfiles/tree/main/.agents/skills/wrdn-code-execution
Command: npx skills add https://github.com/gmcabrita/dotfiles --skill wrdn-code-execution-gmcabrita

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Identify and surface server-side code-execution vulnerabilities when untrusted input reaches a sink that can execute code or commands.

Core Features & Use Cases

Scope includes diffs touching subprocess/exec calls, template rendering, deserialization of bytes, XML parsing, and deep-merge of user-controlled objects across languages.

Quick Start

Tracks source→sink paths, analyzes library usage and gadget chains, and verifies exposure is production-reachable with clear remediation steps.

Frequently Asked Questions about wrdn-code-execution

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

FAQPage Schema
How do I detect server-side code execution vulnerabilities from untrusted input?

You detect server-side code execution vulnerabilities by tracking untrusted source input to execution sinks like subprocess calls, template rendering, or deserialization, verifying production reachability and mapping remediation steps.

What types of execution sinks are analyzed during vulnerability tracing?

Analyzed execution sinks include subprocess and exec calls, template rendering engines, bytes deserialization, XML parsing, and deep-merge operations on user-controlled objects across various programming languages.

How does gadget chain analysis verify production-reachable exposure?

Gadget chain analysis verifies production-reachable exposure by tracking the complete source-to-sink path, examining library usage patterns, and confirming the vulnerability can be triggered in the live production environment.

Can I trace code execution risks in diffs that touch deserialization and XML parsing?

Yes, you can trace code execution risks in diffs touching deserialization of bytes and XML parsing, as the analysis specifically scopes these operations to identify when untrusted input reaches dangerous execution sinks.

What is the best way to remediate untrusted input reaching a command execution sink?

The best way to remediate untrusted input reaching a command execution sink involves following the provided clear remediation steps after the complete source-to-sink path and gadget chain exposure are verified.