wrdn-data-exfil

Trace untrusted input to data-exfiltration sinks and classify findings.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Detects data-exfiltration paths where untrusted input reaches a sink that leaks data beyond its intended scope (SSRF, path traversal, SQL/NoSQL injection enabling bulk reads, XXE file read, response serializers over-exposing internal fields, verbose error pages, logs capturing secrets, and CSV/formula injection in exports).

Core Features & Use Cases

  • Identify sinks and sources across HTTP clients, file I/O with user-provided paths, raw database queries, and export pipelines.
  • Trace data from untrusted inputs to leaks such as cloud metadata exposure, internal service access, or sensitive fields accidentally surfaced in logs or responses.
  • Provide concrete remediation guidance: enforce allowlists, parameterize inputs, scrub logs, and limit data serialization.

Quick Start

Run a diff on a codebase touching HTTP clients, file I/O with user paths, raw queries, XML parsing, or export pipelines to surface potential data-exfiltration paths.

Frequently Asked Questions about wrdn-data-exfil

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

FAQPage Schema
How do I trace untrusted input to data exfiltration sinks in my codebase?

To trace data exfiltration paths, identify where untrusted input reaches sinks like HTTP clients or raw database queries. You must verify guards between the source and sink to prevent leaks such as SSRF, path traversal, and XXE file read vulnerabilities.

What are common data leakage vulnerabilities caused by untrusted input?

Common data leakage vulnerabilities from untrusted input include SSRF, path traversal, SQL/NoSQL injection enabling bulk reads, and XXE file read. These flaws allow untrusted input to reach sinks that expose sensitive data like cloud metadata or internal service details.

How do I detect SSRF and path traversal risks in file I/O operations?

Detect SSRF and path traversal risks by tracing user-provided paths in file I/O operations to see if they reach unintended sinks. Check for missing allowlists or input parameterization that could allow attackers to access internal services or cloud metadata.

Can this approach find sensitive data accidentally exposed in logs and exports?

Yes, this approach finds sensitive data accidentally exposed in logs and exports by tracing untrusted input to response serializers and export pipelines. It identifies if verbose error pages or CSV/formula injection vulnerabilities are leaking secrets beyond their intended scope.

What is the best way to remediate data exfiltration paths once they are found?

The best way to remediate data exfiltration paths is to enforce allowlists, parameterize inputs, scrub logs, and limit data serialization. These concrete steps ensure that untrusted input cannot reach sinks that leak internal fields or execute malicious queries.

Does this method detect vulnerabilities in raw database queries and XML parsing?

Yes, this method detects vulnerabilities in raw database queries and XML parsing by identifying them as data leakage sinks. It traces untrusted input sources to these endpoints to verify if proper guards exist against SQL/NoSQL injection and XXE file read exploits.