跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
安全

webapp-probe

Probe a web app for what it exposes or leaks - passively from captured traffic and actively against the target. Use to assess a web app's exposure or review Burp/ZAP history.

forefy · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add forefy/.context --skill webapp-probe

技能说明


name: webapp-probe description: Probe a web app for what it exposes or leaks - passively from captured traffic and actively against the target. Use to assess a web app's exposure or review Burp/ZAP history.

Contents

  • Scope & authorization (blast-radius labels)
  • Passive analysis of captured traffic:
    1. Missing or weak security headers
    2. Insecure session cookies
    3. Hardcoded secrets & API tokens in bodies
    4. Improper error handling (stack traces, DB errors, debug pages)
    5. Outdated / dev-mode technology fingerprints
    6. RCE-prone parameters in captured requests
  • Active probing of the live target: 7. Disclosure-path brute (.git/config/logs, CVE paths) 8. Outdated / vulnerable software port probe 9. Wayback forgotten-endpoint mining + re-probe 10. Dependency confusion (sourcemaps -> npm)
  • Runnable snippets
  • Output
  • Reference files: references/secret-regexes.md, references/error-signatures.md, references/directory-signatures.md

Scope & authorization

Only run against a web application the user owns or is contractually engaged to test. This skill has two halves, each labelled by blast radius:

  • Passive (classes 1-6) - inspects responses and requests you already captured (proxy history, an authenticated crawl, a saved sitemap, files on disk). Sends no new HTTP requests, mutates nothing, and is safe against a frozen capture.
  • Active (checks 7-10) - sends live requests to the target and, for Wayback (9) and dependency confirmation (10), to third-party services (the Internet Archive, the npm registry). Check 8 is aggressive (multi-port sweep). Run these only in scope, and prefer a low-traffic window.

Take inputs as whatever you already hold: captured responses/requests for the passive half, and the target's domains / domain:port pairs for the active half. Report a finding exactly where each section says "Report a finding when...".

Passive analysis of captured traffic

Each class is one pass over the capture; each yields per-target findings.

0. Extensive attack surface flushout and coverage

Work through the given scope of the target, and work to maximize all the attack surface expansion via all techniques that comes to mind.

Take a webapp for example - seeing a 404 is one thing, but subdomain enumeration expanding the targets, on each running available browser tools to get extended sitemap, available source code, backup files, flush errors and stack traces with unexpected inputs and more.

Coverage is most important as you have to invent and act on lots of variations per the target type tailored to any customization opportunity you may discover that can further the search (e.g. if its next.js version xyz do we know how to trigger errors on there).

1. Missing or weak security headers

For every captured response, case-insensitively collect the response header names and report each of the ten headers below that is absent. Report a finding when: a response is missing any of these. Remediation is "add the <Header> in responses returning from the server".

HeaderWhy it matters
X-Frame-OptionsBlocks embedding the site in iframes (clickjacking).
Content-Security-PolicyControls which resources (e.g. JS) the page may load.
Strict-Transport-SecurityForces HTTPS, including on the initial HTTP connection.
Permissions-PolicyDisables specific browser APIs; propagates to iframes.
X-Content-Type-OptionsStops MIME sniffing; browser trusts only the declared Content-Type.
Referrer-PolicyPrevents leaking sensitive query params via the Referer to third parties.
Cross-Origin-Resource-Policy(xs-leaks) Restricts cross-origin access to the document's resources.
Cross-Origin-Embedder-Policy(xs-leaks) Blocks loading cross-origin resources that don't grant permission via CORP/CORS.
Cross-Origin-Opener-Policy(xs-leaks) Stops popup/opener documents from reaching the page's global object.
Cache-ControlPrevents responses being cached in intermediary proxies and leaked to other users.

2. Insecure session cookies

Look only at cookies that look session-bearing - the cookie name (case-insensitive) contains sess or token. For each such Set-Cookie with a non-empty value, report a finding when any of:

  • No attributes at all - the cookie string has no ; or no =. The whole cookie is insecure.
  • Missing HttpOnly - Cookie '<name>' doesn't have the HTTPOnly attribute set. Fix: set HttpOnly on important cookies.
  • Missing Secure - Cookie '<name>' doesn't have the Secure attribute set. Fix: set Secure.
  • SameSite=None - Cookie '<name>' has the SameSite attribute set to 'none'. Fix: set SameSite=Strict, or at least Lax.
  • Long lifetime - an Expires (parsed as a unix timestamp here) more than 14 days out. Cookie '<name>' has a long expiration date set of more than N days. Fix: give important cookies a short-lived expiration.

Non-session cookies (no sess/token in the name) and empty-valued cookies are skipped to keep the signal high.

3. Hardcoded secrets & API tokens in bodies

Run the secret-regex set in references/secret-regexes.md over every captured response body. Report an INSIGHT (not a hard finding - these are high-value leads that need confirmation) when: any pattern matches. Record <secret name> ( <matched value(s)> ) while requesting <paths>; de-duplicate matches per target and truncate the joined match string to 400 chars.

The set (~40 patterns) covers provider credentials and identifiers: OpenAI/sk-, Slack tokens/webhooks, GitHub classic/fine-grained PATs and git+https URIs, AWS access-key IDs / MWS tokens / S3 bucket URLs, Google API keys / OAuth / GCP service-account JSON / ya29. access tokens, Stripe/Square/PayPal Braintree/Picatic/Mailgun/MailChimp payment & mail keys, DigitalOcean, HuggingFace, Grafana Cloud, Segment, Okta, Fullstory, Adobe, Heroku, Telegram, Firebase URLs, and

阅读完整来源 ↗