YottaMark ShopWell Healthy Diet / Grocery Food Scanner App up to 5.4.2 on iOS X.509 Certificate Validation certificate validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.7 | $0-$5k | 0.00 |
Summary
A vulnerability was found in YottaMark ShopWell Healthy Diet and Grocery Food Scanner App up to 5.4.2 on iOS and classified as critical. This affects an unknown function of the component X.509 Certificate Validation. Such manipulation leads to certificate validation. This vulnerability is uniquely identified as CVE-2017-8942. The attack can be launched remotely. No exploit exists.
Details
A vulnerability, which was classified as critical, has been found in YottaMark ShopWell Healthy Diet and Grocery Food Scanner App up to 5.4.2 on iOS (iOS App Software). Affected by this issue is an unknown code of the component X.509 Certificate Validation. 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 YottaMark ShopWell - Healthy Diet & Grocery Food Scanner app 5.3.7 through 5.4.2 for iOS does not verify X.509 certificates from SSL servers, which allows man-in-the-middle attackers to spoof servers and obtain sensitive information via a crafted certificate.
The bug was discovered 05/05/2017. The weakness was disclosed 05/15/2017 (Website). The advisory is shared for download at medium.com. This vulnerability is handled as CVE-2017-8942 since 05/15/2017. The exploitation is known to be difficult. The attack may be launched remotely. No form of authentication is required for exploitation. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1587.003.
The vulnerability was handled as a non-public zero-day exploit for at least 10 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entries VDB-100866, VDB-100867, VDB-100868 and VDB-100869 are pretty similar. Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.7VulDB Meta Temp Score: 5.7
VulDB Base Score: 5.6
VulDB Temp Score: 5.6
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
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
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
05/05/2017 🔍05/15/2017 🔍
05/15/2017 🔍
05/15/2017 🔍
05/16/2017 🔍
12/29/2019 🔍
Sources
Advisory: medium.comStatus: Not defined
CVE: CVE-2017-8942 (🔍)
GCVE (CVE): GCVE-0-2017-8942
GCVE (VulDB): GCVE-100-101252
See also: 🔍
Entry
Created: 05/16/2017 03:59Updated: 12/29/2019 15:42
Changes: 05/16/2017 03:59 (60), 12/29/2019 15:42 (1)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.