hunt-aspnet

Fingerprint ASP.NET surfaces and triage ViewState security properties.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/AKasem1/claude-bug-bounty --skill hunt-aspnet
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hunt-aspnet
Source: https://github.com/AKasem1/claude-bug-bounty/tree/main/skills/hunt-aspnet
Command: npx skills add https://github.com/AKasem1/claude-bug-bounty --skill hunt-aspnet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you identify and validate high-impact ASP.NET security exposure—especially ViewState deserialization and related framework disclosures—so you can produce actionable bug bounty reports instead of guesswork.

Core Features & Use Cases

  • ASP.NET stack and surface fingerprinting: Detects classic ASP.NET/Webforms indicators (headers, cookies, __VIEWSTATE presence, and version banners) to confirm the right attack surface.
  • ViewState exploitable-surface triage: Determines whether ViewState is signed-only versus encrypted by checking __VIEWSTATEENCRYPTED and runs a parser-error differential to spot dual-entry-point anti-patterns.
  • High-value endpoint discovery & validation: Checks trace.axd and elmah.axd exposure, enumerates WCF .svc metadata, and flags common misconfigurations (customErrors, request-validation gaps).
  • Framework-specific pivots: Guides focused follow-ups for SharePoint farms, Telerik AXD handlers, and SafeControl-related reflection enumeration to complete the exploit chain.

Use case: You have a target URL for an unknown enterprise .NET application; you run this skill to confirm classic ASP.NET/Webforms presence, determine whether ViewState is signed-only, test for disclosure endpoints, and assemble a reproducible evidence chain for your report.

Quick Start

Use the hunt-aspnet skill on a target you can reach over the internet to generate an ASP.NET-specific hunting and triage report focused on ViewState and common disclosure endpoints.

Frequently Asked Questions about hunt-aspnet

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

FAQPage Schema
How do I test ASP.NET ViewState for deserialization vulnerabilities?▼

To test ASP.NET ViewState for deserialization vulnerabilities, you need to fingerprint the application, check if ViewState is signed-only versus encrypted using __VIEWSTATEENCRYPTED, and run parser-error differentials to identify exploitable RCE chains.

What is ViewState triage and how does it expose remote code execution risks?▼

ViewState triage examines __VIEWSTATEENCRYPTED and parser error differentials to detect dual-entry-point anti-patterns. This process exposes remote code execution risks by identifying when ViewState validation is signed-only rather than properly encrypted.

How can I check for exposed trace.axd and elmah.axd endpoints in ASP.NET?▼

You can check for exposed trace.axd and elmah.axd endpoints by probing the target URL for admin endpoint exposure and customErrors misconfigurations, validating these disclosure signals to map high-value information leaks.

Does this approach work for hunting WCF and SharePoint vulnerabilities?▼

Yes, this approach works for hunting WCF and SharePoint vulnerabilities by enumerating .svc metadata, fingerprinting SharePoint farm topology errors, and guiding focused follow-ups for Telerik AXD handlers and SafeControl reflection enumeration.

Can I use this to generate a bug bounty report for .NET application exposure?▼

Yes, you can use this to generate a bug bounty report for .NET application exposure by mapping observable indicators to specific tests and producing a structured, report-ready evidence workflow for reproducible findings.

Why does my ViewState parser throw different errors on the same target?▼

Your ViewState parser throws different errors due to dual-parser behavior and farm topology errors. Running an error-path differential helps spot dual-entry-point anti-patterns indicating framework misconfigurations or signed-only ViewState.