Certificate Pinning Not Implemented
The app trusts any certificate that chains to an authority trusted by the device, without pinning the keys of its own servers.
| Severity | Low |
| CVSS 3.1 | 3.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N Open in the calculator |
| CVSS 4.0 | 2.1 CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:A/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N Open in the calculator |
| CWE | CWE-295: Improper Certificate Validation |
| OWASP Top 10 | A07:2025 Authentication Failures |
| Category | Security Misconfiguration |
Description
Certificate pinning restricts the certificates or public keys an app accepts for its own servers to a known set, instead of any certificate issued by any authority the device trusts. Without pinning, an attacker who can get a certificate for the app's domains trusted by the device can intercept the app's TLS traffic and read and change it. The absence of pinning does not by itself expose traffic: it matters only where an attacker can get such a rogue certificate trusted, through a compromised or coerced certificate authority, a root certificate installed by the user or by a device management system the attacker controls, or a malicious configuration profile the user is persuaded to install and trust.
Current platforms reduce this risk without pinning: Android apps targeting Android 7.0 (API level 24) or higher do not trust user-installed certificate authorities by default, and iOS requires a user-installed root certificate to be explicitly trusted in settings. Pinning is therefore an additional layer, which the OWASP MASVS includes among its network controls (MASVS-NETWORK) for apps that handle highly sensitive data, rather than a baseline requirement.
Without pinning, it is also easier for others to inspect the app's API traffic on their own devices. Testing identifies the absence of pinning by installing an intercepting proxy's root certificate as trusted on a test device, as a system certificate on Android, and observing that the app's traffic can be intercepted.
Remediation
- Decide whether pinning is justified by the app's risk; apps handling payments, health data or other highly sensitive information are the usual candidates.
- Pin the public key (a SHA-256 hash of the SubjectPublicKeyInfo) of the server or of the issuing certificate authority rather than a leaf certificate, include at least one backup pin for a key not yet in use, and plan how pins will be rotated before keys change, since a wrong pin stops the app connecting.
- On Android, use the
pin-setelement of the network security configuration, with an expiration date, or OkHttp'sCertificatePinner; on iOS, use theNSPinnedDomainskey inInfo.plistor a maintained pinning library. - Pin only the organisation's own domains, not third-party services whose keys it does not control.
Confirm the fix by repeating the interception test with a trusted proxy certificate and checking that pinned connections fail, and test the backup pin before relying on it.
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.