container-vuln-testing

Test container runtime vulnerabilities across OCI, Docker, containerd, CRI-O, and Kubernetes layers.

3|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/raesene/rmm-skills --skill container-vuln-testing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: container-vuln-testing
Source: https://github.com/raesene/rmm-skills/tree/main/container-vuln-testing
Command: npx skills add https://github.com/raesene/rmm-skills --skill container-vuln-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires labctl, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill provides a comprehensive framework for testing container runtime vulnerabilities across the entire container stack, helping users identify which layers and components can be exploited and which provide security mitigations.

Core Features & Use Cases

  • Full Container Stack Testing: Evaluate the exploitability of vulnerabilities at various levels (OCI runtime, Docker/containerd/CRI-O, Kubernetes, Node) against runc, crun, containerd, and CRI-O.
  • Layer-by-Layer Analysis: Perform direct testing on the OCI runtime and use labctl playgrounds to simulate different environments for accurate assessments.
  • Integration with labctl: Leverage labctl for managing ephemeral test environments, essential for reproducing and testing vulnerabilities.
  • Use Case: For security researchers or penetration testers aiming to identify potential attack vectors within a containerized application's lifecycle.

Quick Start

Activate the container-vuln-testing skill with container-vuln-testing.

Frequently Asked Questions about container-vuln-testing

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

FAQPage Schema
How do I test container runtime vulnerabilities across runc, containerd, and CRI-O?

Container runtime vulnerability testing validates exploitability across runc, containerd, and CRI-O by analyzing multiple container stack layers. This Skill uses labctl to manage ephemeral test environments for reproducing and validating runtime exploits.

What is the best way to analyze container security at the OCI runtime layer?

Analyzing container security at the OCI runtime layer involves direct testing of runtime components, evaluating which layers provide security mitigations and which can be exploited, from the OCI runtime up through Kubernetes and the Node.

Do I need labctl to run container vulnerability testing?

Yes, labctl is required for container vulnerability testing. It manages the ephemeral test playgrounds and environments essential for simulating different container runtimes and safely reproducing runtime vulnerabilities.

Can I test crun vulnerabilities alongside runc using this framework?

Yes, you can test crun vulnerabilities alongside runc. The framework performs comprehensive testing and validation of vulnerabilities across both OCI runtimes, as well as the containerd and CRI-O container engines.

When do I need to test exploitability across the entire container stack?

Testing exploitability across the entire container stack is needed when identifying potential attack vectors within a containerized application's lifecycle, evaluating vulnerabilities from the OCI runtime up through Docker, Kubernetes, and the Node.

Related Skills