Cleartext Network Traffic Permitted
The app's network security settings permit unencrypted HTTP connections, so traffic to some or all endpoints can be read or changed on the network.
| Severity | Medium |
| CVSS 3.1 | 4.8 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N Open in the calculator |
| CVSS 4.0 | 6.3 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N Open in the calculator |
| CWE | CWE-319: Cleartext Transmission of Sensitive Information |
| OWASP Top 10 | A04:2025 Cryptographic Failures |
| MITRE ATT&CK | T1557 Adversary-in-the-Middle, T1040 Network Sniffing |
| Category | Cryptographic Failures |
Description
Android and iOS both block unencrypted HTTP connections from apps by default and allow apps to relax this in configuration. On Android, cleartextTrafficPermitted="true" in the network security configuration, globally or for specific domains, or the manifest attribute android:usesCleartextTraffic="true", permits cleartext; the default blocks it only for apps targeting Android 9 (API level 28) or higher. On iOS, App Transport Security exceptions in Info.plist, such as NSAllowsArbitraryLoads or NSExceptionAllowsInsecureHTTPLoads for a domain, permit HTTP connections.
The finding is raised when these exceptions are present. An attacker on the same network as the user, such as public Wi-Fi, or elsewhere on the network path, can read any data the app sends over HTTP and change the responses it receives. Depending on the traffic, this can expose credentials and session tokens, leak personal data, or let the attacker inject content into the app, such as altered information, malicious links or scripts in WebViews. The finding is more serious when the app actually sends sensitive data over HTTP; where only non-sensitive resources use HTTP the impact is limited, but the permissive setting leaves room for future mistakes.
Testing identifies it by reviewing the manifest, the network security configuration and Info.plist, and by capturing the app's traffic through an intercepting proxy to see which requests use HTTP. Lower-level networking APIs and some third-party libraries do not honour the platform setting, so traffic capture is needed to be sure.
Remediation
- Serve every endpoint the app uses over HTTPS, and remove the cleartext exceptions.
- On Android, set
cleartextTrafficPermitted="false"in thebase-configof the network security configuration, referenced from the manifest'sandroid:networkSecurityConfigattribute, remove domain exceptions, and do not setandroid:usesCleartextTraffic="true". - On iOS, remove
NSAllowsArbitraryLoadsand per-domainNSExceptionAllowsInsecureHTTPLoadskeys, so that App Transport Security applies to all connections. - Where an exception is unavoidable, for example for a third-party resource that cannot use HTTPS, limit it to that specific domain and make sure no sensitive data passes over it.
Confirm the fix by capturing the app's traffic while exercising all of its features and checking that no request uses HTTP.
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.