detecting-type-confusion
Detects type confusion vulnerabilities by identifying unsafe type casts, vtable corruption, and polymorphism issues. Use when analyzing object-oriented code, type casting, or investigating C++ memory safety issues.
When & Why to Use This Skill
This Claude skill is a specialized security analysis tool designed to detect type confusion vulnerabilities within object-oriented codebases. It focuses on identifying unsafe type casts, vtable corruption, and polymorphism errors, providing developers and security researchers with a systematic workflow to ensure memory safety and prevent critical exploits in C++ and other class-based languages.
Use Cases
- Automated Security Auditing: Scan complex C++ projects to identify hidden memory safety risks, such as unsafe reinterpret_cast operations or unvalidated type conversions.
- Vulnerability Research and Analysis: Assist security analysts in tracing object flows and assessing the exploitability of vtable pointer manipulations or union misuse.
- Secure Software Development: Integrate into the code review process to verify the integrity of class hierarchies and virtual function calls before deployment.
- Legacy Code Maintenance: Analyze older object-oriented systems to find and mitigate potential type-related bugs that could lead to data corruption or code execution.
| name | detecting-type-confusion |
|---|---|
| description | Detects type confusion vulnerabilities by identifying unsafe type casts, vtable corruption, and polymorphism issues. Use when analyzing object-oriented code, type casting, or investigating C++ memory safety issues. |
Type Confusion Detection
Detection Workflow
- Identify type operations: Find all type casts, virtual function calls, union usage, class hierarchies
- Analyze type safety: Check cast validation, assess vtable integrity, verify union usage correctness
- Trace object flow: Use
xrefs_toto trace objects, identify type changes, assess type consistency - Assess exploitability: Can attacker control object type? Is there useful type confusion? Can attacker corrupt vtable?
Key Patterns
- Unsafe type casting: C-style casts without validation, reinterpret_cast without checks
- Vtable corruption: virtual function calls on corrupted objects, vtable pointer manipulation
- Union misuse: writing to one union member, reading another
- Polymorphism issues: base pointer used as derived without dynamic_cast
Output Format
Report with: id, type, subtype, severity, confidence, location, vulnerability, cast operation, base type, derived type, validation, vtable access, exploitability, attack scenario, impact, mitigation.
Severity Guidelines
- CRITICAL: Type confusion with code execution
- HIGH: Type confusion with data corruption
- MEDIUM: Type confusion with limited impact
- LOW: Type confusion with minor issues
See Also
patterns.md- Detailed detection patterns and exploitation scenariosexamples.md- Example analysis cases and code samplesreferences.md- CWE references and mitigation strategies