Vulnerability Note VU#217871

Intel CrossWalk project does not validate SSL certificates after first acceptance

Original Release date: 29 Jul 2016 | Last revised: 29 Jul 2016

Overview

The Intel Crosswalk project is a framework for developing hybrid apps for Android and iOS. The Crosswalk project does not properly handle SSL certificate validation when a user accepts an invalid certificate, preventing the app for validating any future SSL certificates.

Description

CWE-356: Product UI does not Warn User of Unsafe Actions - CVE-2016-5672

When a user makes a network request, an app using the Crosswalk project shows an initial error message if an invalid SSL certificate is found. If the user selects "OK", the app then accepts all future SSL certificates without validation. The app does not make it clear that the dialog grants permanent permission to accept invalid certificates; the user is never prompted again.

The researcher has released a security advisory with more information. Intel has also released a blog post about this issue.

Impact

A victim user that is enticed to accept an invalid SSL certificate actually accepted invalid SSL certificates indefinitely from any source, allowing possible man-in-the-middle attacks in the future from other sources.

Solution

Apply an update

The issue has been resolved in Crosswalk stable 19.49.514.5. Affected users are encouraged to upgrade as soon as possible. Developers should ensure their apps are rebuilt using the latest Crosswalk update.

Vendor Information (Learn More)

VendorStatusDate NotifiedDate Updated
Intel CorporationAffected03 Jun 201629 Jul 2016
If you are a vendor and your product is affected, let us know.

CVSS Metrics (Learn More)

Group Score Vector
Base 5.8 AV:N/AC:M/Au:N/C:P/I:P/A:N
Temporal 4.5 E:POC/RL:OF/RC:C
Environmental 3.4 CDP:ND/TD:M/CR:ND/IR:ND/AR:ND

References

Credit

Thanks to Nightwatch Cybersecurity Research for reporting this vulnerability.

This document was written by Garret Wassermann.

Other Information

  • CVE IDs: CVE-2016-5672
  • Date Public: 29 Jul 2016
  • Date First Published: 29 Jul 2016
  • Date Last Updated: 29 Jul 2016
  • Document Revision: 15

Feedback

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