A static analysis tool for Android applications that detects security vulnerabilities through inter-procedure and intra-procedure analysis.
JAADAS is a static analysis tool for Android applications that detects security vulnerabilities through inter-procedure and intra-procedure analysis. It helps identify issues like API misuse, local denial-of-service (intent crashes), and sensitive data flows from intents to critical APIs. The tool is designed to analyze APKs comprehensively, including multidex applications, and outputs results in JSON format for easy integration.
Android security researchers, penetration testers, and developers who need to audit APKs for vulnerabilities before release or during security assessments.
JAADAS offers a balance between deep, whole-application analysis and fast batch processing, with configurable detection rules that allow customization for specific audit needs. Its integration with Soot provides robust static analysis capabilities, making it a versatile tool for both detailed security reviews and large-scale vulnerability scanning.
Joint Advanced Defect assEsment for android applications
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Seamlessly combines and analyzes multidex applications as a single unit, ensuring comprehensive vulnerability coverage across all dex files without fragmentation.
Allows deep customization of detection through Groovy configuration files and Soot source/sink definitions, enabling tailored security audits for specific needs.
Offers both FullAnalysis for thorough inter-procedure audits and FastAnalysis for quick batch scans, adapting to different assessment scales as noted in the usage modes.
Outputs detailed results in JSON format with method and statement data, facilitating automated processing and integration with other security tools, as shown in the sample output.
FullAnalysis mode requires at least 16GB of RAM, making it impractical for resource-constrained environments and limiting scalability for large applications without high-end hardware.
Based on a 2014 implementation with Soot framework dependencies, it may lack support for modern Android APIs and security vulnerabilities, requiring manual symbolic links for platform jars.
Demands precise Android SDK platform directories and symbolic links for different versions, adding complexity and potential for analysis errors if not configured correctly.