broken-auth-detector

Detect and mitigate OWASP A02 broken authentication vulnerabilities in web applications.

5|1|Updated Feb 4, 2026
One-click install
npx skills add https://github.com/latestaiagents/agent-skills --skill broken-auth-detector
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: broken-auth-detector
Source: https://github.com/latestaiagents/agent-skills/tree/main/plugins/security-guardian/skills/owasp/broken-auth
Command: npx skills add https://github.com/latestaiagents/agent-skills --skill broken-auth-detector

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses critical security vulnerabilities in authentication systems, protecting user accounts from unauthorized access and data breaches.

Core Features & Use Cases

  • Vulnerability Detection: Identifies weak password policies, insecure session management, and flawed JWT implementations.
  • Secure Implementation Guidance: Provides code examples for robust password hashing, secure session handling, and secure JWT usage.
  • Use Case: When reviewing a web application's login and user session management, use this skill to ensure all authentication mechanisms are secure against common attack vectors like session hijacking and credential stuffing.

Quick Start

Use the broken-auth-detector skill to review the authentication flow for potential vulnerabilities.

Frequently Asked Questions about broken-auth-detector

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

FAQPage Schema
How do I detect broken authentication vulnerabilities in my web application?

To detect broken authentication vulnerabilities, analyze login systems, session management, password handling, and authentication flows like JWT, OAuth, and MFA. This process identifies weak password policies and insecure session management to prevent account takeovers.

What are common OWASP A02 session management and JWT implementation flaws?

Common OWASP A02 session management and JWT implementation flaws include insecure session handling, flawed JWT implementations, and weak credential storage. Identifying these vulnerabilities protects user accounts from unauthorized access and session hijacking attacks.

How do I secure JWT implementations and prevent session hijacking?

Secure JWT implementations and prevent session hijacking by applying robust password hashing, secure session handling, and reviewing authentication flows. This approach mitigates common attack vectors like credential stuffing and unauthorized data access.

Can this skill review MFA and OAuth authentication flows for security issues?

Yes, it can review MFA and OAuth authentication flows for security issues. It analyzes these authentication mechanisms alongside password handling and credential storage to identify vulnerabilities and provide secure code patterns.

What is the best way to implement secure password storage and hashing in web applications?

The best way to implement secure password storage and hashing is by using robust code patterns for credential storage. This prevents account takeover by ensuring user credentials are protected against common attack vectors.