Token导航 LogoToken导航TokenDH.com
研究检索操作浏览器github未标认证来源可访问许可证需确认审计异常

pentest-exploit-validation渗透测试利用验证

Agent Skill

用于辅助测试设计、自动化测试、用例整理和回归验证。它适合让 Agent 编写单元测试、端到端测试、测试计划或根据失败日志定位问题。使用时需要确认项目测试框架、运行命令和夹具数据,避免为了通过测试而改坏真实逻辑;涉及浏览器或外部服务时,应区分本地模拟、测试环境和生产环境。

总安装

1,152

周安装

49

GitHub Stars

266

下载量

404
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:pentest-exploit-validation(渗透测试利用验证)
来源仓库:https://github.com/jd-opensource/joysafeter
仓库路径:skills/pentest-exploit-validation
安装命令:
npx skills add https://github.com/jd-opensource/joysafeter --skill pentest-exploit-validation
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/jd-opensource/joysafeter --skill pentest-exploit-validation

简介

验证漏洞可利用性的自动化与半自动化测试框架。

  • 可结合模糊测试、符号执行或污点传播分析判断 RCE/LFI 等高危风险。
  • 输出包括崩溃样本、寄存器状态及调用栈回溯信息。
  • 需确保测试环境与目标版本一致,否则结果可能不可靠。
  • pentest-exploit-validation 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

Pentest Exploit Validation

Purpose

Validate vulnerability findings through proof-driven exploitation using Shannon's 4-level evidence system. Consumes the exploitation queue from white-box code review, attempts structured exploitation with bypass exhaustion, collects mandatory evidence per vulnerability type, and classifies each finding as EXPLOITED, POTENTIAL, or FALSE_POSITIVE.

Prerequisites

Authorization Requirements

  • Written authorization with explicit scope for active exploitation testing
  • Exploitation queue JSON from pentest-whitebox-code-review output
  • Test accounts at multiple privilege levels for authz testing
  • Data exfiltration approval — confirm acceptable proof-of-concept scope
  • Rollback plan for any data-mutating exploits

Environment Setup

  • sqlmap for automated SQL injection exploitation
  • Burp Suite Professional with Repeater, Intruder, and Turbo Intruder
  • curl for manual HTTP request crafting
  • Playwright for browser-based exploitation (XSS, CSRF)
  • nuclei with custom templates for automated validation
  • Isolated testing environment or explicit production testing approval

Core Workflow

  1. Queue Intake: Parse exploitation queue JSON, validate schema, prioritize by confidence score and impact severity. Group findings by vulnerability type for parallel exploitation.
  2. Injection Exploitation: Confirm injectable parameter → fingerprint backend (DB type, OS) → enumerate databases/tables → demonstrate data exfiltration with minimal footprint.
  3. XSS Exploitation: Graph traversal from source → processing → sanitization → sink. Craft context-appropriate payload, demonstrate session hijack or DOM manipulation.
  4. Auth Exploitation: Attack authentication weaknesses → demonstrate account takeover via credential stuffing, token forgery, or session hijack.
  5. Authz Exploitation: Horizontal access (cross-user data) → vertical escalation (admin functions) → workflow bypass (state manipulation).
  6. SSRF Exploitation: Internal service access → cloud metadata retrieval (169.254.169.254) → internal network reconnaissance.
  7. Bypass Exhaustion: For each finding, attempt 3 initial payloads → if blocked, escalate to 8-10 bypass variations → if still blocked, deploy automated tool variants.
  8. Impact Escalation: Escalate from proof-of-concept to real impact demonstration — data exfiltration, session hijacking, or remote code execution.
  9. Evidence Collection: Collect mandatory evidence per vulnerability type using per-type checklists.
  10. Classification: Assign final classification — EXPLOITED, POTENTIAL, or FALSE_POSITIVE — based on 4-level proof system.

4-Level Proof System

LevelDescriptionClassification
L1Weakness identified in code but not confirmed exploitablePOTENTIAL
L2Partial bypass achieved but full exploitation not demonstratedPOTENTIAL
L3Vulnerability confirmed with reproducible evidenceEXPLOITED
L4Critical impact demonstrated (data exfil, RCE, account takeover)EXPLOITED CRITICAL

Classification Criteria

ClassificationCriteria
EXPLOITEDReproducible proof with evidence: HTTP request/response, extracted data, or demonstrated impact
POTENTIALCode-level weakness confirmed but exploitation blocked by defense-in-depth or environment constraints
FALSE_POSITIVETaint analysis flagged but manual review confirms effective sanitization or unreachable code path

Tool Categories

CategoryToolsPurpose
SQL Injectionsqlmap, manual payloadsAutomated and manual SQLi exploitation
Request CraftingBurp Repeater, curlManual HTTP request manipulation
FuzzingBurp Intruder, Turbo IntruderPayload variation and bypass testing
Browser ExploitationPlaywrightXSS demonstration, session hijack
Automationnuclei, custom scriptsTemplate-based vulnerability validation
Evidence CaptureBurp Logger, screenshot toolsRequest/response logging and proof

References

  • references/tools.md - Tool function signatures and parameters
  • references/workflows.md - Exploitation workflows, evidence checklists, and classification tree

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

39.12%
按下载量换算158

Claude

28.66%
按下载量换算116

Cursor

17.53%
按下载量换算71

Gemini CLI

10.35%
按下载量换算42

安全审计

Gen Agent Trust Hub

未通过

Socket

通过

Snyk

未通过

权限和风险

操作浏览器

该 Skill 可能涉及浏览器控制能力,使用时可能读取或操作网页内容,需要在受控环境中确认权限边界。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills