Common APK Security Vulnerabilities
快速回答
Common APK issues include exported components without permission checks, insecure storage, weak TLS, leaked secrets, and debug leftover in release builds.
Common APK security vulnerabilities are defects in how the app is built. They are distinct from malware, though malware often abuses the same APIs.
Exported components
Activities, services and receivers with exported="true" and no permission check can be invoked by other apps. If they return data or trigger money movement, that is a finding.
Data storage
Unencrypted SharedPreferences or files with sensitive tokens. Backup flags that include session material.
Transport
Cleartext HTTP, custom trust managers that accept any certificate, leaked pinning bypasses.
Secrets in the APK
API keys, HMAC secrets, private URLs. Assume anyone can unzip a release.
Debug leftovers
android:debuggable="true" on a store build. Verbose logging of PII.
These show up in a security assessment. Broader product risks: Android application security risks. Permissions that enable abuse: permission analysis.
要点
- Many 'vulnerabilities' are misconfigured components, not exotic exploits.
- Release builds should not be debuggable and should not ship leftover keys.
- Cleartext traffic and world-readable files still appear in real apps.
实践指引
- 01Review the merged manifest for exported=true without permissions.
- 02Search release APKs for API keys and private endpoints before you ship.
下一步怎么做
常见问题
Is an exported activity always a vulnerability?
No. It is a vulnerability when it exposes data or actions without auth that should be private. Export is a feature for launchers and deep links when intended.
Does Play scanning mean these are gone?
Play catches some issues. It does not replace your own review of components and secrets.
Are these the same as malware?
No. Vulnerabilities are defects in software you might ship. Malware is hostile purpose. Both can exist in one APK.
相关问题