hunt-session

Tests web applications for session fixation, invalidation, and token lifecycle vulnerabilities.

1|Updated Aug 21, 2026
One-click install
npx skills add https://github.com/marcboggs/BMAD-AppSec-Orchestrator --skill hunt-session-marcboggs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hunt-session
Source: https://github.com/marcboggs/BMAD-AppSec-Orchestrator/tree/main/.claude/skills/hunt-session
Command: npx skills add https://github.com/marcboggs/BMAD-AppSec-Orchestrator --skill hunt-session-marcboggs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Session management flaws like fixation, missing logout invalidation, and unrotated refresh tokens enable persistent account takeover, yet they are hard to prove without rigorous two-session testing and false-positive discipline. ## Core Features & Use Cases - Lifecycle Invalidation Testing: Verify sessions are killed on logout, password change, and email change using real attacker/victim session pairs captured via curl cookie jars. - Fixation & Entropy Analysis: Detect session IDs not regenerated on login, attacker-forced session values, and predictable or low-entropy identifiers through large-sample statistical analysis. - Token & Cookie Hardening Review: Audit refresh-token rotation and reuse-detection, JWT-as-session expiry/revocation, DBSC downgrade, and Secure/HttpOnly/SameSite/__Host- cookie attributes. - Use Case: During a bug bounty engagement, capture a test account's session, change its password from a second session, then replay the old cookie against /api/me — if it still returns user data, you have proven a persistent account-takeover finding. ## Quick Start Test whether the target's session is invalidated after logout and password change using the two-session curl methodology.

Frequently Asked Questions about hunt-session

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

FAQPage Schema
How do I test for session fixation vulnerabilities?▼

Capture a pre-authentication session cookie, log in while carrying that cookie, then compare the session value before and after authentication. If the value is unchanged and now returns authenticated data, the server failed to regenerate the session ID, confirming fixation.

How to check if a session is invalidated after password change?▼

Log in twice to create sessions A and B, change the password using session B, then replay session A against a protected endpoint. If it still returns the account's unique data, the old session survived the credential change, proving persistent account takeover risk.

What is refresh token rotation and reuse detection?▼

Rotation means each refresh request returns a new refresh token, invalidating the old one. Reuse detection means replaying an old token revokes the entire token family. Without both, a leaked refresh token can mint access tokens indefinitely.

Why does a 200 response not prove a session vulnerability?▼

Cached edge responses or generic SPA shells return 200 for everyone. You must body-diff the response against an authenticated baseline for unique identity markers, and confirm a garbage cookie fails as a negative control.

When is a missing HttpOnly cookie attribute a real finding?▼

Missing HttpOnly is only a meaningful finding when chained to a real XSS or DOM sink that can exfiltrate the cookie. Standalone attribute gaps are Low or Informational severity until paired with an actual exploit primitive.