detecting-null-pointer-dereference
Detects null pointer dereference vulnerabilities by identifying unchecked pointer usage and missing validation. Use when analyzing pointer operations, input validation, or investigating crash vulnerabilities.
When & Why to Use This Skill
This Claude skill automates the detection of null pointer dereference vulnerabilities by analyzing pointer operations and identifying missing validation logic. It helps developers and security researchers prevent application crashes and security exploits by tracing pointer sources and verifying null checks across complex code paths, significantly improving software reliability and security posture.
Use Cases
- Security Vulnerability Scanning: Automatically identify and mitigate potential null pointer dereferences in large codebases to prevent system crashes or denial-of-service (DoS) attacks.
- Automated Code Quality Assurance: Enhance the peer review process by catching unchecked pointer usage and missing input validations in real-time before code is merged into production.
- Root Cause Analysis for Crashes: Investigate software crashes by tracing pointer origins and identifying the specific code paths where null validation is missing or incomplete.
- API and Library Hardening: Audit public-facing APIs to ensure all pointer parameters are rigorously validated, preventing crashes caused by unexpected null inputs from external callers.
| name | detecting-null-pointer-dereference |
|---|---|
| description | Detects null pointer dereference vulnerabilities by identifying unchecked pointer usage and missing validation. Use when analyzing pointer operations, input validation, or investigating crash vulnerabilities. |
Null Pointer Dereference Detection
Detection Workflow
- Identify pointer dereferences: Find all pointer dereferences (*ptr, ptr->field), array accesses (ptr[index]), function calls with pointer parameters, pointer operations
- Trace pointer sources: Use
xrefs_toto trace pointers, find where pointers originate, identify pointer assignments, track pointer values - Check null validation: Verify null checks before dereference, assess check completeness, identify missing validation paths, check validation logic correctness
- Assess impact: Can attacker control pointer value? Is dereference reachable? What's the crash potential? Can it lead to security issues?
Key Patterns
- Missing null checks: pointer dereference without null check, function calls with unchecked pointers, array access through null pointers, member access through null pointers
- Conditional dereference: dereference after partial null check, dereference in only some code paths, dereference after pointer assignment, dereference in loop conditions
- Function parameter issues: unchecked function parameters, assumptions about non-null parameters, missing validation in public APIs, null pointers from external sources
- Return value issues: dereferencing potentially null return values, assuming malloc/new never returns null, missing checks on function returns, dereferencing failed allocations
Output Format
Report with: id, type, subtype, severity, confidence, location, dereferenced_pointer, dereference_type, dereference_operation, pointer_source, null_check, vulnerability, exploitable, attack_scenario, impact, mitigation.
Severity Guidelines
- HIGH: Null dereference in critical code paths
- MEDIUM: Null dereference causing crashes
- LOW: Null dereference with limited impact
See Also
patterns.md- Detailed detection patterns and exploitation scenariosexamples.md- Example analysis cases and code samplesreferences.md- CWE references and mitigation strategies