Description

Insecure device pairing results in an insecure communication between two physical devices. Device-pairing protocols configured are vulnerable to the misbinding attacks, it arises from the lack of verifiable identifiers.

Impact

- Spoof, intercept and modify messages in the network in arbitrary ways. - Allow malicious behavior by one of the intended communication endpoints.

Recommendation

- Establish a shared cryptographic key between two or more communication endpoints to use the shared key for protecting communication integrity and confidentiality. - Specify security properties as correspondence assertions in addition to basic authentication properties, it can help to detect subtle flaws that might otherwise go unnoticed.

Threat

Attacker may impersonate one of the device communication endpoints or set itself as a man in the middle (MitM) between them.

Expected Remediation Time

⏱️ 300 minutes.

Details

https://mobile-security.gitbook.io/mobile-security-testing-guide/android-testing-guide/0x05j-testing-resiliency-against-reverse-engineering#owasp-masvs

Requirements

Fixes