The secureApk tool analyzes Android APK files for security vulnerabilities, such as cryptographic weaknesses, data leakage, and insecure storage. This README explains how to use the provided Docker images to run the tool on your system.
Before starting, ensure the following:
The secureApk tool is available as Docker images for both ARM64 and AMD64 architectures. Use the appropriate docker pull command based on your system:
For ARM64 systems:
docker pull devrvk/secureapk:arm64
For AMD64 systems:
docker pull devrvk/secureapk:amd64
input in your current working directory:
mkdir input
input directory. For example:
input/
└── your-app.apk
Note: The tool requires exactly one APK file in the input directory. Multiple or no APK files will cause the analysis to fail.
output in your current working directory:
mkdir output
Run the Docker container with the following command, replacing <image-tag> with either arm64 or amd64 depending on your system’s architecture:
docker run -v $(pwd)/input:/input -v $(pwd)/output:/output devrvk/secureapk:<image-tag>
This command:
input directory from your current working directory to /input inside the container.output directory to /output inside the container.secureApk tool to analyze the APK file and save the results.After the analysis completes, check the output directory on your host machine. The results will be stored there, along with a log file named analysis.log containing the terminal output from the analysis.
For example:
output/
├── vulnerabilities.txt
└── [other result files of decompiled apk]
output directory is writable by the Docker container (e.g., the container runs as root, so the directory must allow root write access).output directory. To save previous results, use a different output directory for each analysis (e.g., output1, output2).Content type
Image
Digest
sha256:eb9d05a4a…
Size
371.8 MB
Last updated
over 1 year ago
docker pull devrvk/secureapk:amd64