vuln-memory

Detect memory-safety vulnerabilities in C/C++/Rust native code and append findings to vulnerabilities.md.

Updated Jun 23, 2024
One-click install
npx skills add https://github.com/n4igme/randscript --skill vuln-memory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vuln-memory
Source: https://github.com/n4igme/randscript/tree/main/llm/skills/scode/vuln-memory
Command: npx skills add https://github.com/n4igme/randscript --skill vuln-memory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Step 3p of bug bounty workflow. Scan for memory safety vulnerabilities (buffer overflow, use-after-free, format strings) in C/C++/Rust/native code. Appends to vulnerabilities.md.

Core Features & Use Cases

  • Detects memory-corruption patterns across C, C++, and Rust unsafe blocks and native extensions.
  • Maps findings to a structured vulnerability report appended to vulnerabilities.md for auditing and remediation.
  • Use Case: Team wants to continuously monitor repositories with native code for memory-safety issues and maintain a centralized risk log.

Quick Start

Run the vuln-memory scanner against your codebase to identify memory-safety vulnerabilities and append findings to vulnerabilities.md.

Frequently Asked Questions about vuln-memory

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

FAQPage Schema
How do I scan C/C++/Rust native code for memory-safety vulnerabilities?

Memory-safety vulnerabilities like buffer overflows and use-after-free are detected by applying static analysis rules to source trees containing unsafe blocks, FFI boundaries, or native extensions. The scanner identifies memory-corruption patterns and formats findings into a structured report appended to vulnerabilities.md.

How do I detect buffer overflows and use-after-free in unsafe Rust blocks?

To detect buffer overflows and use-after-free in unsafe Rust blocks, run a static scanner that analyzes memory-management calls and unsafe patterns within the source tree. It identifies corruption risks and appends structured findings to vulnerabilities.md for auditing and remediation.

Does memory-corruption scanning work with FFI boundaries and native extensions?

Memory-corruption scanning works with FFI boundaries and native extensions by applying static analysis rules across C, C++, and Rust unsafe code. The scanner requires access to the source tree to map detected vulnerabilities into a structured vulnerabilities.md report.

What is the best way to continuously monitor repositories for memory-safety issues?

Continuously monitor repositories for memory-safety issues by running a static analysis scanner against native codebases to detect memory-corruption patterns. Each scan appends structured findings to vulnerabilities.md, maintaining a centralized risk log for auditing and remediation.

Can I generate a structured vulnerability report for native code auditing?

You can generate a structured vulnerability report for native code auditing by scanning the source tree for unsafe patterns and memory-management calls. The scanner appends detected buffer overflows, use-after-free, and format-string vulnerabilities directly to vulnerabilities.md.