207 – Security controls bypass or absence - SSLPinning
Description
The application does not define an SSLPinning mechanism or configures it insecurely, allowing an attacker to intercept and manipulate the information that travels through the application
Impact
- Intercept data from the app. - Tamper data from the app.
Recommendation
- Implement robust security controls for certificates, offering either a predefined set of trusted Certification Authorities or incorporating integrity checks and white lists of trusted public keys that the application will accept. - In res/xml/network_security_config.xml - Define pin-sets with integrity hashes. - Set trust-anchors by providing a list of trusted Certification Authorities.
Threat
Anonymous attacker from the Internet.
Expected Remediation Time
Score 4.0
Default score using CVSS 4.0. It may change depending on the context of the src.
Base 4.0
- Attack vector: P
- Attack complexity: L
- Attack Requirements: N
- Privileges required: N
- User interaction: N
- Confidentiality (VC): L
- Integrity (VI): L
- Availability (VA): N
- Confidentiality (SC): N
- Integrity (SI): N
- Availability (SA): N
Threat 4.0
- Exploit maturity: P