fix-vulnerability

Automate vm2 vulnerability remediation from GHSA or CVE advisories.

4.1k|326|Updated Jan 14, 2014
One-click install
npx skills add https://github.com/patriksimek/vm2 --skill fix-vulnerability
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-vulnerability
Source: https://github.com/patriksimek/vm2/tree/main/.claude/skills/fix-vulnerability
Command: npx skills add https://github.com/patriksimek/vm2 --skill fix-vulnerability

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end process of patching vm2 sandbox vulnerabilities by translating security advisories (GHSA/CVE) into actionable fixes, testing plans, and documentation updates.

Core Features & Use Cases

  • Advisory-driven patching: Accepts GHSA or CVE IDs, fetches the advisory, and reproduces the PoC to inform the fix.
  • Structural remediation workflow: Designs and applies structural fixes to the vm2 sandbox, writes tests, and updates ATTACKS.md.
  • Validation and governance: Performs red-team validation and keeps security documentation in sync for audit trails.

Quick Start

Provide a GHSA- or CVE-ID to start the patch workflow and produce a patched vm2 release.

Frequently Asked Questions about fix-vulnerability

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

FAQPage Schema
How do I patch vm2 vulnerabilities using a GHSA or CVE ID?

To patch vm2 vulnerabilities, provide a GHSA or CVE ID to fetch the advisory, reproduce the PoC, perform root-cause analysis, and apply a structural fix with tests. This workflow automates end-to-end remediation for the vm2 sandbox.

Can I automate root-cause analysis for vm2 security advisories?

Yes, vm2 security advisories are automatically translated into actionable patch workflows. The process fetches advisory details via GitHub CLI, reproduces the proof of concept, and conducts root-cause analysis to design a structural fix for the sandbox.

Do I need the GitHub CLI to reproduce vm2 vulnerability PoCs?

Yes, you need the GitHub CLI to fetch repository security advisories. Reproducing the vm2 vulnerability PoC requires gh CLI access and the project docs/ATTACKS.md file to guide structural mitigations and keep documentation in sync.

What is the best way to document vm2 vulnerability patches for audit trails?

The best way to document vm2 vulnerability patches is updating the ATTACKS.md file. The workflow performs red-team validation and keeps security documentation in sync, ensuring governance and a reliable audit trail for the remediated sandbox.

Why does vm2 vulnerability patching require red-team validation?

Red-team validation is required during vm2 vulnerability patching to verify the structural fix holds against attacks. It conducts adversarial testing after the patch and tests are applied, ensuring the sandbox escape is fully remediated before release.

What limitations exist when fixing vm2 sandbox escapes with security advisories?

Fixing vm2 sandbox escapes requires access to repository security advisories, the GitHub CLI, and an existing docs/ATTACKS.md file. Without these dependencies, the end-to-end vulnerability remediation workflow cannot fetch advisories or guide mitigations.