broken-authentication

Featured

This skill should be used when the user asks to "test for broken authentication vulnerabilities", "assess session management security", "perform credential stuffing tests", "evaluate password policies", "test for session fixation", or "identify authentication bypass flaws". It provides comprehensive techniques for identifying authentication and session management weaknesses in web applications.

API & Backend 4,617 stars 463 forks Updated today MIT

Install

View on GitHub

Quality Score: 96/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Broken Authentication Testing ## Purpose Identify and exploit authentication and session management vulnerabilities in web applications. Broken authentication consistently ranks in the OWASP Top 10 and can lead to account takeover, identity theft, and unauthorized access to sensitive systems. This skill covers testing methodologies for password policies, session handling, multi-factor authentication, and credential management. ## Prerequisites ### Required Knowledge - HTTP protocol and session mechanisms - Authentication types (SFA, 2FA, MFA) - Cookie and token handling - Common authentication frameworks ### Required Tools - Burp Suite Professional or Community - Hydra or similar brute-force tools - Custom wordlists for credential testing - Browser developer tools ### Required Access - Target application URL - Test account credentials - Written authorization for testing ## Outputs and Deliverables 1. **Authentication Assessment Report** - Document all identified vulnerabilities 2. **Credential Testing Results** - Brute-force and dictionary attack outcomes 3. **Session Security Analysis** - Token randomness and timeout evaluation 4. **Remediation Recommendations** - Security hardening guidance ## Core Workflow ### Phase 1: Authentication Mechanism Analysis Understand the application's authentication architecture: ``` # Identify authentication type - Password-based (forms, basic auth, digest) - Token-based (JWT, OAuth, API keys) - Certificate-based (mutual TLS) - ...

Details

Author
zebbern
Repository
zebbern/claude-code-guide
Created
1 years ago
Last Updated
today
Language
Python
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

API & Backend Listed

sast-missingauth

Detect missing authentication and broken function-level authorization vulnerabilities in a codebase using a three-phase approach: recon (map endpoints and the role/permission system), batched verify (check auth/authz in parallel subagents, 3 endpoints each), and merge (consolidate batch results). Covers unauthenticated access and vertical privilege escalation (e.g., regular user accessing admin-only functions). Requires sast/architecture.md (run sast-analysis first). Outputs findings to sast/missingauth-results.md. Use when asked to find missing auth, broken access control, or privilege escalation bugs.

1 Updated today
reasonless-throne486
Web & Frontend Listed

auth-hardening

Review, harden, and design authentication and session management for web applications — login, logout, session lifecycle, password storage, token handling, and brute-force protection. Use this skill whenever the user is building or reviewing sign-in / sign-out flows, JWT or session cookies, password hashing, "remember me", refresh tokens, account lockout, OTP/MFA, or password reset — even if they only mention "login" or "auth" casually. Applies to Node.js, Next.js, and similar stacks. Defensive only: this skill hardens auth systems, it does not bypass or attack them.

1 Updated 2 weeks ago
AL-JANEF
Web & Frontend Listed

web-vulnhunt

Authorized security testing methodology for web apps, APIs, multi-tenant SaaS, Spring Boot / Cloud Gateway stacks, FIDO/WebAuthn passwordless auth, mobile backends, and OAuth/SSO integrations. Use whenever the user asks to test, probe, scan, find vulnerabilities in, or pentest any web service — including bug bounty engagements, authorized pentests, CTF challenges, post-patch re-verification, CVSS scoring, subdomain/asset discovery, WAF/auth-filter bypass, **authorization bypass / IDOR / broken access control / missing @PreAuthorize / privilege escalation** testing, FIDO2/UAF testing, token-chain analysis, or writing vulnerability reports. Also triggers on the words "AcmeAuth", "Keycloak", "Okta", "PingFederate", "Auth0", or any passwordless-auth vendor. This is a defensive skill for authorized work only — always confirm scope before any active test.

7 Updated 2 weeks ago
do-whilefor