Insteon Hub 1012 HTTP Server sn_speaker memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.6 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in Insteon Hub 1012. Affected by this issue is some unknown functionality of the component HTTP Server. Performing a manipulation of the argument sn_speaker as part of HTTP Request results in memory corruption. This vulnerability is identified as CVE-2017-16344. The attack can be initiated remotely. There is not any exploit available.
Details
A vulnerability was found in Insteon Hub 1012 (Network Management Software). It has been classified as critical. This affects some unknown processing of the component HTTP Server. The manipulation of the argument sn_speaker 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 attacker could send an authenticated HTTP request to trigger this vulnerability in Insteon Hub running firmware version 1012. At 0x9d01c2c8 the value for the s_url key is copied using strcpy to the buffer at 0xa0001a0c. This buffer is 16 bytes large, sending anything longer will cause a buffer overflow. The destination can also be shifted by using an sn_speaker parameter between "0" and "3".
The bug was discovered 06/19/2018. The weakness was released 08/02/2018 (Website). The advisory is shared at talosintelligence.com. This vulnerability is uniquely identified as CVE-2017-16344 since 10/30/2017. The exploitability is told to be easy. It is possible to initiate the attack remotely. Required for exploitation is a authentication. Technical details are known, but no exploit is available.
The vulnerability was handled as a non-public zero-day exploit for at least 44 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.
Entries connected to this vulnerability are available at VDB-122535, VDB-122536, VDB-122537 and VDB-122538. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.6VulDB Meta Temp Score: 8.6
VulDB Base Score: 7.4
VulDB Temp Score: 7.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.9
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
10/30/2017 🔍06/19/2018 🔍
08/02/2018 🔍
08/02/2018 🔍
08/03/2018 🔍
04/29/2023 🔍
Sources
Advisory: talosintelligence.comStatus: Not defined
CVE: CVE-2017-16344 (🔍)
GCVE (CVE): GCVE-0-2017-16344
GCVE (VulDB): GCVE-100-122541
See also: 🔍
Entry
Created: 08/03/2018 07:20Updated: 04/29/2023 11:38
Changes: 08/03/2018 07:20 (60), 03/12/2020 19:49 (1), 04/29/2023 11:38 (12)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.