CtrlK
BlogDocsLog inGet started
Tessl Logo

hunt-saml

Hunt SAML / SSO attacks. Patterns: XML Signature Wrapping (XSW) — modify Assertion while keeping Signature valid by relocating signed element, comment injection in NameID (admin@target.com<!--evil-->@attacker.com → some parsers see admin@target.com), signature stripping (remove Signature element entirely, server should reject but doesn't), key confusion (signed by attacker's IdP, accepted by SP), audience-restriction not validated, replay attack (same Assertion accepted twice within validity window). Tools: SAML Raider Burp extension, samlmagic, manual XML manipulation. Detection: any /saml endpoint, /Shibboleth.sso, /sso/saml/, Microsoft ADFS endpoints. Validate: account takeover via altered NameID, admin role injection via altered AttributeStatement. Use when hunting SSO flows, when SAML AssertionConsumerService is reachable, when chaining IdP-trust to SP-impersonation.

70

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

The body is a highly actionable SAML/SSO hunting playbook with executable commands, exact payloads, and a useful triage table, well-organized into clear sections. Its weaknesses are verbosity in the Related Skills chain primitives (which restate already-shown attacks) and the absence of in-workflow validate/verify feedback loops for the XML-manipulation steps.

Suggestions

Tighten the 'Related Skills & Chains' entries: name the chain primitive in one line instead of re-narrating the full XSW/signature-stripping flow that the body already demonstrates.

Add an explicit validation checkpoint inside each attack workflow (e.g., 'Confirm the altered assertion is accepted AND that the resulting session has elevated privileges before claiming severity') rather than deferring all validation to the triage-validation skill.

In the Attack 3 signature-stripping steps, add a verify step between re-encode and submit (e.g., confirm the stripped response no longer contains a Signature element) so the destructive change is checked before submission.

DimensionReasoningScore

Conciseness

The attack sections are dense and assume SAML/XML knowledge, but the 'Related Skills & Chains' block re-explains the full XSW/signature-stripping mechanics in prose for each linked skill, restating attacks already shown above rather than just naming the chain primitive.

2 / 3

Actionability

Provides copy-paste-ready commands (`echo "BASE64" | base64 -d | xmllint --format -`, `base64 -w0 saml.xml`), exact XML payloads, concrete tool instructions (SAML Raider Burp tab), and specific NameID test values with CVE references.

3 / 3

Workflow Clarity

Attack 3 has a clear 1-5 numbered sequence and a triage table maps outcomes to severity, but the XML-manipulation workflows lack an explicit validate→fix→retry feedback loop inside the workflow — validation is deferred out to the referenced triage-validation skill.

2 / 3

Progressive Disclosure

Single-file skill with no bundle directories; content is organized into clean, navigable sections (Attack Surface, Attacks 1-5, Tools, Triage, Related Skills) and cross-references other skills at one level deep with no nested indirection.

3 / 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.

The description is specific, complete, and distinct: it enumerates concrete SAML/SSO attack patterns, tools, detection endpoints, and validation goals, then closes with an explicit 'Use when' trigger clause. It is dense but every clause earns its place and it uses third-person voice throughout.

DimensionReasoningScore

Specificity

Lists multiple concrete attack actions — 'XML Signature Wrapping (XSW)', 'comment injection in NameID', 'signature stripping', 'key confusion', 'replay attack' — each tied to a concrete mechanism, plus named tools (SAML Raider, samlmagic) and detection endpoints.

3 / 3

Completeness

Explicitly answers what ('Hunt SAML / SSO attacks' with patterns, tools, detection, validate steps) and when (an explicit 'Use when hunting SSO flows...' clause with multiple triggers).

3 / 3

Trigger Term Quality

Natural terms a hunter would say are present — 'SAML / SSO attacks', 'Use when hunting SSO flows', 'SAML AssertionConsumerService is reachable' — alongside concrete endpoint patterns (/saml, /Shibboleth.sso, ADFS).

3 / 3

Distinctiveness Conflict Risk

A sharply defined SAML/SSO niche with SAML-specific triggers ('AssertionConsumerService is reachable', 'IdP-trust to SP-impersonation') makes it unlikely to fire for non-SAML skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
elementalsouls/Claude-BugHunter
Reviewed

Table of Contents

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.