Analyze Flutter and mobile applications for OWASP Mobile Top 10 (2024) security compliance...
pubspec.yamlComprehensive security analysis for Flutter and mobile applications based on OWASP Mobile Top 10 (2024).
Four Python scanners cover the most automatable risk categories. Replace <skill-dir> with the skill's install path (e.g. ~/.claude/skills/owasp-mobile-security-checker):
python3 <skill-dir>/scripts/scan_hardcoded_secrets.py /path/to/project
Detects API keys, tokens, passwords, AWS credentials, and Firebase keys in Dart code and config files.
python3 <skill-dir>/scripts/check_dependencies.py /path/to/project
Analyzes pubspec.yaml for outdated packages, any version constraints, and known CVEs.
python3 <skill-dir>/scripts/check_network_security.py /path/to/project
Checks HTTP vs HTTPS usage, certificate pinning, Android Network Security Config, and iOS ATS settings.
python3 <skill-dir>/scripts/analyze_storage_security.py /path/to/project
Identifies unencrypted SharedPreferences, plaintext file storage, unencrypted databases, and insecure backup configurations.
M3, M4, M6, M7, M8, and M10 require code review. See references/owasp_mobile_top_10_2024.md for Flutter-specific vulnerability patterns, attack flows, and remediation for each category.
Is this a comprehensive audit?
āā YES ā Run all 4 scanners ā Review JSON outputs ā Manual analysis (M3/M4/M6/M7/M8/M10) ā Generate report
āā NO ā Continue...
Specific risk category?
āā M1 ā scan_hardcoded_secrets.py
āā M2 ā check_dependencies.py
āā M5 ā check_network_security.py
āā M9 ā analyze_storage_security.py
āā M3/M4/M6/M7/M8/M10 ā references/owasp_mobile_top_10_2024.md ā manual analysis
Quick pre-release check?
āā YES ā Run all 4 scanners ā Fix CRITICAL and HIGH findings only
# Run all automated scanners from the project root
python3 <skill-dir>/scripts/scan_hardcoded_secrets.py .
python3 <skill-dir>/scripts/check_dependencies.py .
python3 <skill-dir>/scripts/check_network_security.py .
python3 <skill-dir>/scripts/analyze_storage_security.py .
# Outputs produced:
# owasp_m1_secrets_scan.json
# owasp_m2_dependencies_scan.json
# owasp_m5_network_scan.json
# owasp_m9_storage_scan.json
references/owasp_mobile_top_10_2024.md| Risk | Issue | Automated? | Key Check |
|---|---|---|---|
| M1 | Hardcoded credentials | ā scanner | API keys, tokens in source/config |
| M2 | Vulnerable dependencies | ā scanner | Outdated or unconstrained packages |
| M3 | Weak authentication | Manual | Token storage, MFA, session expiry |
| M4 | Input validation | Manual | SQL injection, XSS in WebViews, IDOR |
| M5 | Insecure communication | ā scanner | HTTP usage, missing cert pinning |
| M6 | Privacy violations | Manual | PII in logs/analytics, excess permissions |
| M7 | No binary protections | Manual | Missing --obfuscate, no root detection |
| M8 | Misconfiguration | Manual | Debug flags in production, verbose logging |
| M9 | Insecure storage | ā scanner | Sensitive data in SharedPreferences |
| M10 | Weak cryptography | Manual | MD5/SHA1/ECB usage, hardcoded keys |
| Severity | Meaning | Action |
|---|---|---|
| CRITICAL | Exploitable immediately | Fix now ā do not release |
| HIGH | Significant vulnerability | Fix before release |
| MEDIUM | Should be addressed | Plan for next sprint |
| LOW | Best practice improvement | Address as time permits |
YOUR_API_KEYlocalhost/127.0.0.1 in developmentAlways verify findings in context before flagging as vulnerabilities.
pubspec.yamlreferences/owasp_mobile_top_10_2024.md provides per-risk detail:
| Stage | Action |
|---|---|
| Pre-commit | Run scan_hardcoded_secrets.py as a lightweight secrets gate |
| Pull requests | Run all 4 scanners, post findings as PR comment |
| Release builds | Full audit including manual analysis for all 10 categories |
| Incident response | Run targeted scanner for the reported vulnerability category |