Twitter Client 6.62/6.62.1 on iOS Server Certificate Validator /1.1/help/settings.json certificate validation
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
5.4 | $0-$5k | 0.00 |
A vulnerability, which was classified as critical, has been found in Twitter Client 6.62/6.62.1 on iOS (Social Network Software). Affected by this issue is an unknown function of the file /1.1/help/settings.json of the component Server Certificate Validator. The manipulation with an unknown input leads to a certificate validation vulnerability. Using CWE to declare the problem leads to CWE-295. The product does not validate, or incorrectly validates, a certificate. Impacted is confidentiality, integrity, and availability. CVE summarizes:
The Twitter iOS client versions 6.62 and 6.62.1 fail to validate Twitter's server certificates for the /1.1/help/settings.json configuration endpoint, permitting man-in-the-middle attackers the ability to view an application-only OAuth client token and potentially enable unreleased Twitter iOS app features.
The bug was discovered 12/23/2016. The weakness was presented 09/18/2017 (Website). The advisory is available at securityfocus.com. This vulnerability is handled as CVE-2016-10511 since 09/18/2017. The exploitation is known to be difficult. The attack may be launched remotely. No form of authentication is required for exploitation. Successful exploitation requires user interaction by the victim. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1587.003 by the MITRE ATT&CK project.
The vulnerability was handled as a non-public zero-day exploit for at least 269 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:1.1/help/settings.json it is possible to find vulnerable targets with Google Hacking.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB CVSS-B Score: 🔍VulDB CVSS-BT Score: 🔍
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.4
VulDB Base Score: 5.0
VulDB Temp Score: 5.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.9
NVD Vector: 🔍
CVSSv2
AV | AC | Au | C | I | A |
---|---|---|---|---|---|
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
---|---|---|---|---|---|
unlock | unlock | unlock | unlock | unlock | unlock |
unlock | unlock | unlock | unlock | unlock | unlock |
unlock | unlock | unlock | unlock | unlock | unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Certificate validationCWE: CWE-295 / CWE-287
ATT&CK: T1587.003
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
Google Hack: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
0-Day | unlock | unlock | unlock | unlock |
---|---|---|---|---|
Today | unlock | unlock | unlock | unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
12/23/2016 🔍09/18/2017 🔍
09/18/2017 🔍
09/18/2017 🔍
09/18/2017 🔍
09/19/2017 🔍
01/13/2021 🔍
Sources
Advisory: securityfocus.com⛔Researcher: floyd.
Status: Not defined
CVE: CVE-2016-10511 (🔍)
SecurityFocus: 100904
Entry
Created: 09/19/2017 08:53Updated: 01/13/2021 12:07
Changes: 09/19/2017 08:53 (61), 11/17/2019 10:55 (1), 01/13/2021 12:07 (4)
Complete: 🔍
No comments yet. Languages: en.
Please log in to comment.