Code Obfuscation Not Applied
The application's code is shipped without obfuscation, so decompiling it gives readable class, method and field names that make its logic easy to study.
| Severity | Informational |
| CVSS 3.1 | 0 CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N Open in the calculator |
| CVSS 4.0 | 0 CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:N/SA:N Open in the calculator |
| CWE | CWE-693: Protection Mechanism Failure |
| OWASP Top 10 | A06:2025 Insecure Design |
| Category | Security Misconfiguration |
Description
The application package is built without code obfuscation, so its compiled code can be turned back into readable source with freely available tools. Android applications written in Java or Kotlin compile to DEX bytecode, which decompilers such as jadx reconstruct closely, including the original class, method and field names unless a tool such as R8 has renamed them. Cross-platform frameworks often ship code in an even more accessible form, such as the JavaScript bundle of a Cordova application or the .NET assemblies of a Xamarin or .NET MAUI application. iOS applications compile to native code, which is harder to read, but Objective-C class and method names are kept in the binary for the runtime and can be listed with tools such as class-dump, and other symbol names remain unless the release build is stripped.
An attacker can therefore quickly understand how the application works: its API endpoints and parameters, how requests are signed, how client-side checks such as root detection or certificate pinning are implemented, and where keys and tokens are handled. This shortens the work needed to find other weaknesses, to bypass client-side controls with instrumentation tools, to build automated clients that imitate the application, or to produce repackaged copies for fraud.
The weakness is identified by decompiling the release build and finding meaningful names throughout the application's own code, debug information such as source file names and line numbers, and descriptive strings that explain its logic. Tools such as APKiD, which MobSF includes, identify known obfuscators and packers in Android packages.
Obfuscation is a resilience measure that raises the cost of reverse engineering, but it only delays a capable reverse engineer, and it does not protect secrets embedded in the code, which are a separate finding. The absence of obfuscation does not directly expose data, so the finding is informational unless the application depends on its code staying secret.
Remediation
Enable obfuscation for every release build, and keep broad exceptions from undoing it:
- On Android, turn on R8 code shrinking and obfuscation in the release build type, and keep
-keeprules as narrow as possible, limited to classes reached through reflection, serialisation or native code. A rule that keeps a whole package removes most of the benefit. - Keep the mapping file that R8 produces private, and upload it to the Play Console so that crash reports can still be read.
- For Flutter, build with
--obfuscateand--split-debug-info. For other cross-platform frameworks, use the framework's release optimisation and an obfuscator suited to its code format. - On iOS, strip symbols from release builds using Xcode's symbol stripping build settings (such as
Strip Linked ProductandStrip Style), and avoid self-describing names for security-relevant classes and methods. - For applications with high-value logic, consider a commercial protector that adds string encryption, control flow obfuscation and anti-tampering, as R8 renames identifiers but does not encrypt strings.
- Move secrets and security decisions to the server, as obfuscation hides them only from casual inspection.
Confirm the fix by decompiling the release build with jadx, or a disassembler for iOS, and checking that the application's own classes and methods no longer carry meaningful names.
References
Add This Finding to Your Library
In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.
Free trialYour trial starts when your portal goes live, not when you sign up, so the time you spend setting up does not count. · No card required
Only need the reporting? Our reporting tool is free and open source, with the same library.