U by BB&T iOS banking application fails to properly validate SSL certificates
Original Release date: 30 Sep 2016 | Last revised: 06 Oct 2016

Overview
U by BB&T for iOS, version 1.5.4 and earlier, fails to properly validate SSL certificates provided by HTTPS connections, which may enable an attacker to conduct man-in-the-middle (MITM) attacks.

Description

CWE-295: Improper Certificate Validation – CVE-2016-6550
U by BB&T is a banking application. On iOS devices, the app fails to properly validate SSL certificates provided by HTTPS connections, which means that an attacker in the position to perform MITM attacks may be able to obtain sensitive account information such as login credentials.

Impact

An attacker on the same network as the iOS device may be able to view or modify network traffic that should have been protected by HTTPS, which may lead to the exposure of sensitive account information, including login credentials.

Solution

Update the app to the latest versionVersion 1.5.5 appears to have addressed the issue.

Do not use affected versions of the applicationThe features and services provided by the application are likely accessible via the BB&T banking web site.

By using a web browser to access those resources, you may avoid situations where SSL is not validated.Avoid untrusted networksAvoid using untrusted networks, including public WiFi. Using your device on an untrusted network increases the chance of falling victim to a MITM attack.

Vendor Information (Learn More)
Vendor
Status
Date Notified
Date Updated
BB&T Bank
Affected
16 Aug 2016
22 Sep 2016
If you are a vendor and your product is affected, let us know.
CVSS Metrics (Learn More)
Group
Score
Vector
Base
7.8
AV:A/AC:L/Au:N/C:C/I:C/A:N
Temporal
7.0
E:F/RL:W/RC:C
Environmental
1.8
CDP:ND/TD:L/CR:ND/IR:ND/AR:ND

References

Credit
Thanks to the reporter who wishes to remain anonymous.
This document was written by Joel Land.

Other Information
CVE IDs: CVE-2016-6550
Date Public: 30 Sep 2016
Date First Published: 30 Sep 2016
Date Last Updated: 06 Oct 2016
Document Revision: 21

Feedback
If you have feedback, comments, or additional information about this vulnerability, please send us email.

Leave a Reply