MQTT.js up to 2.14.x PUBLISH Ticket resource management
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in MQTT.js up to 2.14.x. Affected by this issue is some unknown functionality of the component PUBLISH Ticket Handler. The manipulation leads to resource management. This vulnerability is referenced as CVE-2017-10910. Remote exploitation of the attack is possible. No exploit is available. It is advisable to upgrade the affected component.
Details
A vulnerability, which was classified as problematic, has been found in MQTT.js up to 2.14.x (JavaScript Library). This issue affects an unknown functionality of the component PUBLISH Ticket Handler. The manipulation with an unknown input leads to a resource management vulnerability. Using CWE to declare the problem leads to CWE-399. Impacted is availability. The summary by CVE is:
MQTT.js 2.x.x prior to 2.15.0 issue in handling PUBLISH tickets may lead to an attacker causing a denial-of-service condition.
The bug was discovered 12/25/2017. The weakness was published 12/28/2017 (Website). It is possible to read the advisory at jvn.jp. The identification of this vulnerability is CVE-2017-10910 since 07/04/2017. The exploitation is known to be easy. The attack may be initiated remotely. The successful exploitation needs a simple authentication. The technical details are unknown and an exploit is not publicly available.
The vulnerability was handled as a non-public zero-day exploit for at least 2 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version 2.15.0 eliminates this vulnerability.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.5
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: Resource managementCWE: CWE-399 / CWE-404
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: MQTT.js 2.15.0
Patch: github.com
Timeline
07/04/2017 🔍12/25/2017 🔍
12/27/2017 🔍
12/28/2017 🔍
12/28/2017 🔍
01/19/2023 🔍
Sources
Advisory: 403ba53b838f2d319a0c0505a045fe00239e9923Status: Not defined
CVE: CVE-2017-10910 (🔍)
GCVE (CVE): GCVE-0-2017-10910
GCVE (VulDB): GCVE-100-111035
Entry
Created: 12/28/2017 09:36Updated: 01/19/2023 08:03
Changes: 12/28/2017 09:36 (58), 12/18/2019 07:47 (1), 01/19/2023 08:03 (6)
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.