Insteon Hub up to 1012 PubNub Message HTTP Request memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.5 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Insteon Hub up to 1012. Affected is an unknown function of the component PubNub Message Handler. Performing a manipulation as part of HTTP Request results in memory corruption. This vulnerability is cataloged as CVE-2017-14447. It is possible to initiate the attack remotely. There is no exploit available. It is suggested to use restrictive firewalling.
Details
A vulnerability was found in Insteon Hub up to 1012 (Network Management Software). It has been classified as critical. This affects some unknown functionality of the component PubNub Message Handler. The manipulation as part of a HTTP Request leads to a memory corruption vulnerability. CWE is classifying the issue as CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
An exploitable buffer overflow vulnerability exists in the PubNub message handler for the 'ad' channel of Insteon Hub running firmware version 1012. Specially crafted commands sent through the PubNub service can cause a stack-based buffer overflow overwriting arbitrary data. An attacker should send an authenticated HTTP request to trigger this vulnerability.
The bug was discovered 06/19/2018. The weakness was shared 08/06/2018 (Website). The advisory is shared at talosintelligence.com. This vulnerability is uniquely identified as CVE-2017-14447 since 09/13/2017. It is possible to initiate the attack remotely. A authentication is required for exploitation. Neither technical details nor an exploit are publicly available.
The vulnerability was handled as a non-public zero-day exploit for at least 48 days. During that time the estimated underground price was around $0-$5k.
It is possible to mitigate the weakness by firewalling .
The entry VDB-122650 is related to this item. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.5VulDB Meta Temp Score: 7.5
VulDB Base Score: 6.3
VulDB Temp Score: 6.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.7
NVD Vector: 🔍
CNA Base Score: 8.5
CNA Vector (Talos): 🔍
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: Memory corruptionCWE: CWE-119
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: FirewallStatus: 🔍
0-Day Time: 🔍
Timeline
09/13/2017 🔍06/19/2018 🔍
08/06/2018 🔍
08/06/2018 🔍
08/07/2018 🔍
05/01/2023 🔍
Sources
Advisory: talosintelligence.comStatus: Not defined
CVE: CVE-2017-14447 (🔍)
GCVE (CVE): GCVE-0-2017-14447
GCVE (VulDB): GCVE-100-122649
See also: 🔍
Entry
Created: 08/07/2018 07:16Updated: 05/01/2023 08:15
Changes: 08/07/2018 07:16 (60), 03/13/2020 16:19 (1), 05/01/2023 08:15 (14)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.