Skip to content
StrikeOps

Missing Certificate Pinning in a Mobile App

InformationalTypical severity Mobile applicationsCWE-295

01Description

The application accepted any certificate trusted by the device, including user-installed certificates, rather than pinning to its own server certificate or key.

02Impact

On devices where an attacker or an organization has installed a trusted root certificate, the app's traffic can be intercepted and modified. This also makes reverse engineering of the API easier.

03Severity

Typically

Informational

Typically Informational. Informational for most apps. Low to Medium for high-risk apps such as banking, where the threat model includes intercepting devices with installed root certificates.

04How to verify

  1. 1Install a test root certificate on a test device and proxy the app's traffic.
  2. 2Confirm whether connections succeed and traffic is readable.

Testing note: only test systems you are authorized to test, within the agreed scope and rules of engagement. Verification steps are written for professional testers and avoid destructive techniques.

05Remediation

  1. 1For high-risk apps, pin to the public key of the server or an intermediate, with a backup pin and an update plan.
  2. 2On Android, ensure the network security config does not trust user-installed certificates.
  3. 3Treat pinning as defense in depth; the API must remain secure without it.

06References

Draft findings like this from your own evidence

Book a demo
Book a demo