| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.5 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in igniteui up to 0.0.5 on Node.js. This impacts an unknown function. This manipulation causes 7pk security. This vulnerability is registered as CVE-2016-10552. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability has been found in igniteui up to 0.0.5 on Node.js (JavaScript Library) and classified as critical. Affected by this vulnerability is some unknown functionality. The manipulation with an unknown input leads to a 7pk security vulnerability. The CWE definition for the vulnerability is CWE-254. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
igniteui 0.0.5 and earlier downloads JavaScript and CSS resources over insecure protocol.
The bug was discovered 12/16/2016. The weakness was published 05/31/2018 (Website). It is possible to read the advisory at nodesecurity.io. This vulnerability is known as CVE-2016-10552 since 10/29/2017. The attack can be launched remotely. The exploitation doesn't need any form of authentication. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1211 according to MITRE ATT&CK.
The vulnerability was handled as a non-public zero-day exploit for at least 531 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.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.5VulDB Meta Temp Score: 6.5
VulDB Base Score: 5.6
VulDB Temp Score: 5.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.4
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: 7pk securityCWE: CWE-254
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
12/16/2016 🔍10/29/2017 🔍
05/31/2018 🔍
05/31/2018 🔍
06/01/2018 🔍
02/10/2020 🔍
Sources
Advisory: nodesecurity.ioStatus: Not defined
CVE: CVE-2016-10552 (🔍)
GCVE (CVE): GCVE-0-2016-10552
GCVE (VulDB): GCVE-100-118435
Entry
Created: 06/01/2018 09:39Updated: 02/10/2020 13:27
Changes: 06/01/2018 09:39 (57), 02/10/2020 13:27 (1)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.