Information Disclosure Detection
Detection Workflow
- Identify sensitive data flows: Find where sensitive data is handled, trace data through application, identify all output points
- Check logging practices: Analyze log statements, check error messages, review debug output
- Assess exposure points: Identify all user-facing output, check external API responses, review file system artifacts
- Evaluate impact: What information is disclosed? How sensitive is it? Who can access it?
Key Patterns
- Sensitive data in logs: passwords, keys, stack traces in production logs
- Error message disclosure: detailed errors revealing system info, paths, database queries
- Memory disclosure: uninitialized memory reads, out-of-bounds reads, format string leaks
- Storage disclosure: plaintext storage, weak encryption, insecure file permissions
Output Format
Report with: id, type, subtype, severity, confidence, location, sensitive data type, disclosure point, vulnerability description, exposure scope, risk, mitigation.
Severity Guidelines
- CRITICAL: Disclosure of cryptographic keys or passwords
- HIGH: Disclosure of sensitive user data
- MEDIUM: Disclosure of system information
- LOW: Disclosure of minor debug information
See Also
patterns.md - Detailed detection patterns and exploitation scenariosexamples.md - Example analysis cases and code samplesreferences.md - CWE references and mitigation strategies
Converted and distributed by TomeVault — claim your Tome and manage your conversions.
1---2name: detecting-information-disclosure3description: Detects information disclosure vulnerabilities including sensitive data in logs, error message exposure, and memory leaks. Use when analyzing logging practices, error handling, or investigating data leakage issues. Use when this capability is needed.4---56# Information Disclosure Detection78## Detection Workflow9101. **Identify sensitive data flows**: Find where sensitive data is handled, trace data through application, identify all output points112. **Check logging practices**: Analyze log statements, check error messages, review debug output123. **Assess exposure points**: Identify all user-facing output, check external API responses, review file system artifacts134. **Evaluate impact**: What information is disclosed? How sensitive is it? Who can access it?1415## Key Patterns1617- Sensitive data in logs: passwords, keys, stack traces in production logs18- Error message disclosure: detailed errors revealing system info, paths, database queries19- Memory disclosure: uninitialized memory reads, out-of-bounds reads, format string leaks20- Storage disclosure: plaintext storage, weak encryption, insecure file permissions2122## Output Format2324Report with: id, type, subtype, severity, confidence, location, sensitive data type, disclosure point, vulnerability description, exposure scope, risk, mitigation.2526## Severity Guidelines2728- **CRITICAL**: Disclosure of cryptographic keys or passwords29- **HIGH**: Disclosure of sensitive user data30- **MEDIUM**: Disclosure of system information31- **LOW**: Disclosure of minor debug information3233## See Also3435- `patterns.md` - Detailed detection patterns and exploitation scenarios36- `examples.md` - Example analysis cases and code samples37- `references.md` - CWE references and mitigation strategies3839---40> Converted and distributed by [TomeVault](https://tomevault.io/claim/waiwai24) — claim your Tome and manage your conversions.41<!-- tomevault:4.0:skill_md:2026-04-13 -->
tomevault-io