Security pattern / case archive

Security Misconfiguration

A deployment or server configuration exposes resources or behavior that the documented security boundary did not intend.

Common discovery signals
  • Directory listing or default server behavior reveals deployment residue.
  • Production resources conflict with removal or access expectations in deployment notes.
Safe validation approach

Confirm the specific exposed behavior with minimal read-only requests and avoid inferring unrelated configuration weaknesses.

Related classifications

Related entries

Archive connections

Connected case files

04 records
CASE-023WEBVERSE
Connected evidence

CrocThis

Exposed Git Repository / Trusted Header Authentication Bypass

A public .git directory exposed the PHP authorization path. The same /admin/ request changed from 403 to 200 after adding the source-derived X-User identity, and both Caido and curl reached the protected operations console.

Browser / Caido / Terminal / Python / curl
CASE-018WEBVERSE
Connected evidence

PrinPrin

Default Password / Administrative Access

An invalid login stayed on the public sign-in page, while admin/admin redirected to the printer dashboard. Caido and curl then reached the authenticated admin view and its remote service key.

Browser / Caido / curl
CASE-013WEBVERSE
Connected evidence

Margin Notes

Missing Authentication / Public Source Map Disclosure

Margin Notes exposed a source map containing the route and response handling for a hidden diagnostic endpoint. One anonymous Caido request returned build data, runtime details, and the lab flag.

Browser / Caido
CASE-003WEBVERSE
Connected evidence

Dust Jacket

Sensitive Backup and Credential Exposure

An Apache directory listing exposed config.php.bak with a reusable OWNER_KEY. The owner console rejected an invalid key but accepted the exposed value without Cookie or Authorization headers.