Cryptographic Weakness Detection
Detection Workflow
- Identify cryptographic functions: Search for crypto-related function names, encryption/decryption operations, hash function usage
- Extract crypto parameters: Identify algorithms used, check key sizes and modes, examine IV/nonce handling
- Check for hardcoded secrets: Use
strings to find potential keys, search for common password/key patterns, analyze data sections for secrets
- Assess implementation security: Check for constant-time comparisons, verify proper padding, assess randomness of IVs/nonces
Key Patterns
- Weak algorithms: DES, 3DES, RC4, MD5, SHA1, ECB mode, small key sizes (<128 bits)
- Hardcoded secrets: passwords/passphrases, keys, IVs/nonces, magic numbers
- Insecure key management: keys embedded in code, plaintext storage, weak RNG, reused IVs/nonces
- Implementation issues: timing attacks, side-channel vulnerabilities, incorrect padding, missing authentication
Output Format
Report with: id, type, subtype, severity, confidence, location, algorithm, mode, key_size, issues, recommendation, cve_references, mitigation.
Severity Guidelines
- CRITICAL: Hardcoded private keys or passwords
- HIGH: Broken algorithms (DES, RC4) in security-critical code
- MEDIUM: Weak algorithms in non-critical code
- LOW: Minor crypto implementation issues
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: analyzing-crypto-weakness3description: Identifies weak cryptographic algorithms, hardcoded keys, and insecure key management practices in binary code. Use when analyzing encryption/decryption, authentication mechanisms, or reviewing cryptographic implementations. Use when this capability is needed.4---56# Cryptographic Weakness Detection78## Detection Workflow9101. **Identify cryptographic functions**: Search for crypto-related function names, encryption/decryption operations, hash function usage112. **Extract crypto parameters**: Identify algorithms used, check key sizes and modes, examine IV/nonce handling123. **Check for hardcoded secrets**: Use `strings` to find potential keys, search for common password/key patterns, analyze data sections for secrets134. **Assess implementation security**: Check for constant-time comparisons, verify proper padding, assess randomness of IVs/nonces1415## Key Patterns1617- Weak algorithms: DES, 3DES, RC4, MD5, SHA1, ECB mode, small key sizes (<128 bits)18- Hardcoded secrets: passwords/passphrases, keys, IVs/nonces, magic numbers19- Insecure key management: keys embedded in code, plaintext storage, weak RNG, reused IVs/nonces20- Implementation issues: timing attacks, side-channel vulnerabilities, incorrect padding, missing authentication2122## Output Format2324Report with: id, type, subtype, severity, confidence, location, algorithm, mode, key_size, issues, recommendation, cve_references, mitigation.2526## Severity Guidelines2728- **CRITICAL**: Hardcoded private keys or passwords29- **HIGH**: Broken algorithms (DES, RC4) in security-critical code30- **MEDIUM**: Weak algorithms in non-critical code31- **LOW**: Minor crypto implementation issues3233## 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 -->
