Skip to content
Skills Library
Security · Review & audit

debug-endpoint-exposure

/debug-endpoint-exposure

Look for framework debug, health and introspection routes reachable without the authentication the rest of the API requires. Use when the route inventory includes debug, metrics, health or introspection paths

Repository
flawpath ↗
Licence
MIT
Last repository change
28.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
2
Deprecation

No signals detected. Repository changed on 28.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Look for framework debug, health and introspection routes reachable without the authentication the rest of the API requires. Use when the route inventory includes debug, metrics, health or introspection paths

Original author description

Look for framework debug, health and introspection routes reachable without the authentication the rest of the API requires. Use when the route inventory includes debug, metrics, health or introspection paths

How it works

  1. Procedure
  2. Signals
  3. Patterns
  4. Pitfalls
  5. Done when
  6. References
Original SKILL.md headings · 64 lines, 373 words
SKILL.md preview
---
name: debug-endpoint-exposure
description: "Look for framework debug, health and introspection routes reachable without the authentication the rest of the API requires. Use when the route inventory includes debug, metrics, health or introspection paths"
pack: flawpath
version: 1.0.0
category: backend-api
tags: [probe, debug, routes]
---

# Debug Endpoint Exposure

> Look for framework debug, health and introspection routes reachable without the authentication the rest of the API requires

**Use when:** the route inventory includes debug, metrics, health or introspection paths

**Avoid when:** those routes are all behind authentication and a test confirms a rejection for each

## Procedure

1. List every debug, metrics, health, and introspection path from the route inventory.
2. Request each without credentials and record status, body and timing against the baseline.
3. For any that answer, record which fields the body exposes: configuration, routes, versions or environment.
4. Check whether the environment delta explains the exposure, since debug routes often follow a debug flag.
5. Note whether these paths are excluded from logging while others are logged.
6. Record each path with reachable, rejected or absent as its verdict, plus what a reachable one disclosed.

## Signals

- A debug or introspection route answers without authentication
- A metrics endpoint reveals internal names, counts or versions
- An unauthenticated route returns configuration detail absent from normal responses
- A debug path is excluded from the access log

## Patterns

**1. Route verdict**

```text
path | auth required | status | discloses | in log
/debug/routes | no | 200 | full route table | no
/metrics | no | 200 | version and counts | yes
/health | no | 200 | nothing sensitive | yes
```

**2. Environment link**

```text
tie each exposure back to the environment delta, since a debug route enabled by a flag is a configuration finding
```

**3. Logging note**

```text
record whether the path is logged; an unlogged debug route is a second finding on the same path
```

## Pitfalls

- Reporting a health endpoint as exposed without saying what it actually disclosed
- Missing that a debug route is gated by an environment flag rather than by authentication
- Ignoring that the route may be excluded from logs, which changes the response

## Done when

- Every debug and introspection path has a verdict with what it disclosed if reachable
- Each exposure is linked to the environment delta and its logging status

## References

- [OWASP - Security misconfiguration](https://owasp.org/Top10/A05_2021-Security_Misconfiguration/)
- [CWE-489 - Active debug code](https://cwe.mitre.org/data/definitions/489.html)

Versions

The database has no other skills named debug-endpoint-exposure.

Database snapshot: 13.11.2026 · package version 3cbc031bae34 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100debug-surface-disabled-in-shared-environments
    Turn off debug, introspection and verbose error paths in any environment more than one person can reach, and verify by request rather than by configuration reading. Use when a debug or introspection route is reachable or verbose errors are enabled outside a local environment
  • 96agent-introspection-debugging
    キャプチャ、診断、封じ込め回復、内省レポートを使用した AI エージェント障害のための構造化された自己デバッグワークフロー。
  • 90graphql-security
    Detects GraphQL schemas without depth limits, cost analysis, or introspection controls. Use when writing GraphQL schemas, resolvers, or server configuration. Also invoke when setting up Apollo Server, graphql-yoga, Strawberry, gqlgen, or any GraphQL framework without explicit…
  • 100secure-api-endpoint
    Use when adding or modifying an API endpoint by hand (route, handler, serializer, validation, authorization policy). Applies the two-layer auth model, public-identifier-only exposure, tenant-safe persistence and the input, query, upload and log checklist.
  • 100stack-trace-exposure
    Use when reviewing error handling middleware, API route handlers, or server responses for security-sensitive information disclosure.
  • 95api-security-review
    Use when developer explicitly asks to review an endpoint, controller, service, or API for security issues. Also triggers on: "review this for security", "is this secure", "check this endpoint", "security audit", "what are the vulnerabilities here", or when asked to review a full…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.