hunt-aspnet

Audits ASP.NET and IIS applications for misconfigurations, authentication flaws, and CVE exposure.

10|3|Updated Aug 10, 2026
One-click install
npx skills add https://github.com/baiqigo/baiqi-redteam-lab --skill hunt-aspnet-baiqigo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hunt-aspnet
Source: https://github.com/baiqigo/baiqi-redteam-lab/tree/main/.agents/skills/hunt-aspnet
Command: npx skills add https://github.com/baiqigo/baiqi-redteam-lab --skill hunt-aspnet-baiqigo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Security testers need a disciplined, evidence-gated workflow for assessing ASP.NET/IIS targets without jumping to unsafe exploitation. This Skill structures the audit of error pages, debug configuration, routing, ViewState handling, file upload, authentication, and historical CVE applicability while enforcing strict stop conditions. ## Core Features & Use Cases - Evidence-Gated Triage: Confirms server, framework, module, and version evidence before any probe, treating banners and stack traces as inconclusive signals rather than vulnerabilities. - Safe Validation Workflow: Uses baseline, single-variable probe, post-baseline, oracle, and evidence steps with owned low-privilege accounts and test data only. - Specialist Routing: Hands off deserialization findings to hunt-deserialization, file issues to hunt-file-upload or hunt-lfi, and CVE checks to the main orchestrator route. - Use Case: During an authorized engagement you discover .aspx endpoints and a __VIEWSTATE field; the Skill guides you to audit MAC/encryption configuration and error handling without constructing executable ViewState payloads. ## Quick Start Ask the agent to run the ASP.NET specialist audit against the authorized target after confirming scope, baseline, and that this route ranks in the orchestrator's top three.

Frequently Asked Questions about hunt-aspnet

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

FAQPage Schema
How do I audit an ASP.NET application for security misconfigurations?

Start by confirming server, framework, module, and version evidence, then review customErrors, debug settings, authentication mode, routing, and file handling. Use owned low-privilege accounts to compare authorization differences on error pages and admin surfaces.

How to test ViewState security without exploiting it?

Audit the MAC, encryption, and user-binding configuration evidence plus error handling behavior rather than constructing payloads. The presence of a __VIEWSTATE field alone is not a vulnerability; only configuration weaknesses confirmed non-destructively count as findings.

Does an IIS banner or .NET stack trace confirm a vulnerability?

No. Exception stack traces, __VIEWSTATE presence, and IIS banners are treated as inconclusive signals, not vulnerabilities. A valid finding requires sensitive debug or management data accessible to an identity that should not have it, or confirmed version and exposure matching a security condition.

When should ASP.NET testing stop during an engagement?

Stop immediately when a step would write files, execute payloads, read configuration secrets, touch non-test ViewState data, exceed scope, affect third parties or shared users, or cause irreversible side effects. WAF blocks, captchas, and timeouts are recorded as inconclusive.

Can this audit handle deserialization or file upload findings?

It routes them to specialist skills instead of testing them directly. Deserialization candidates go to hunt-deserialization, file handling issues go to hunt-file-upload or hunt-lfi, and CVE-specific checks return to the main orchestrator route.