vmware-vcenter-attack

VMware vSphere / vCenter Server external attack matrix — version fingerprinting, the high-impact CVE chain (CVE-2021-21972 vRealize unauth file upload, CVE-2021-21985 vSAN plugin RCE, CVE-2022-22954 Workspace ONE SSTI, CVE-2023-20887 Aria RCE, CVE-2024-37085 ESXi AD bypass, CVE-2023-34048 vCenter DCERPC OOB write APT-exploited), default credentials, SSO configuration disclosure, vmdir LDAP enumeration, ESXi Open SLP RCE history. ONLY for vCenter / Workspace ONE / Aria instances exposed to the internet — internal-network vCenter is out of scope per the external-only boundary. Use when recon shows port 443 with vCenter banner, `/ui` redirect, `/websso/SAML2/Metadata`, or VMware product fingerprints.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Operationally excellent: executable probes, a well-sequenced workflow with real validation gates, and strong safety/boundary discipline. It loses points on conciseness and progressive disclosure because the deep CVE-disclosure reference material is dumped inline in SKILL.md rather than externalized into a reference file.

Suggestions

Move the "Disclosed CVEs & coordinated-disclosure citations" appendix (per-CVE root-cause, disclosure history, and reference URL lists) into a references/ file (e.g., CVE_REFERENCES.md) and replace it in SKILL.md with a one-line pointer, shrinking the inline footprint substantially.

Trim the per-CVE prose to the operationally essential fields (affected versions + vector + patch status) in the main matrix; keep researcher names, CISA KEV dates, and Mandiant attribution in the externalized reference only.

Group time-sensitive version numbers and patch dates under a clearly labeled section so they can be updated in one place without inflating the operational steps.

Dimension	Reasoning	Score
Conciseness	The operational curl probes are lean, but the body carries a large inline "Disclosed CVEs & coordinated-disclosure citations" appendix with per-CVE root-cause, disclosure history, researcher names, and 4 reference URLs each — material that pads context with time-sensitive detail Claude can largely look up. Not a 1 because the command blocks themselves are tight and executable; not a 3 because the citation prose could be trimmed or externalized.	2 / 3
Actionability	Concrete, copy-paste-ready curl commands with interpreted status codes ("405 → endpoint exists, version vulnerable", "404 → patched"), a canary-based RCE confirmation logic, and a build→version→CVE mapping step — fully executable guidance rather than abstraction.	3 / 3
Workflow Clarity	A clear Step 1→10 sequence with explicit validation checkpoints: Stage A detection vs Stage B execution gated on "explicit RCE-attempt sign-off", a body-diff canary check ("Confirmed RCE ONLY if the response contains the exact $CANARY... absent from baseline"), and a hard "If recon reveals vCenter only via VPN → STOP" boundary check. Destructive operations carry validation/sign-off gates, so the destructive-cap is not triggered.	3 / 3
Progressive Disclosure	No bundle files exist (references/scripts/assets absent) and the SKILL.md is monolithic — the ~90-line disclosure-citations section and full CVE reference URLs are inline material that should live in a separate reference file. Sections are clearly labeled (some structure), but content that should be split out is not, and there are no one-level-deep references to signal.	2 / 3
	Total	10 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, highly specific description with an explicit "Use when..." trigger, clear niche boundaries, and third-person voice. Its only weakness is verbosity — embedding six CVE IDs inline adds length without improving activation — but every required element is present.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "version fingerprinting", "default credentials", "SSO configuration disclosure", "vmdir LDAP enumeration", "ESXi Open SLP RCE" — each tied to named CVEs, matching the "lists multiple specific concrete actions" anchor.	3 / 3
Completeness	Explicitly answers both what (the attack matrix and its concrete actions) and when via the clause "Use when recon shows port 443 with vCenter banner, /ui redirect, /websso/SAML2/Metadata, or VMware product fingerprints."	3 / 3
Trigger Term Quality	Natural terms a red-team user would say are present and prominent — "vCenter", "vSphere", "VMware", "port 443 with vCenter banner", "/ui redirect" — giving good coverage of real trigger language rather than pure jargon.	3 / 3
Distinctiveness Conflict Risk	Tightly scoped to "VMware vSphere / vCenter Server external attack" with product-specific triggers and an explicit out-of-scope boundary ("internal-network vCenter is out of scope"), making it unlikely to fire for the wrong skill.	3 / 3
	Total	12 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: elementalsouls/Claude-BugHunter
Path: skills/vmware-vcenter-attack/SKILL.md
Commit: 6b9c96e

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.