Notre sélection d'alertes et avis SSI.
Sources : US Cert, Cert EU, Cert FR, Cnil, VulDB.

lundi 8 octobre 2018

Microsoft MQTT Object memory corruption [CVE-2018-8531]

A vulnerability was found in Microsoft Azure IoT Edge and Hub Device Client SDK for Azure IoT (the affected version is unknown). It has been rated as critical. Affected by this issue is an unknown function of the component MQTT Object Handler. The manipulation with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to CWE-119. Impacted is confidentiality, integrity, and availability.

The weakness was released 10/09/2018 as confirmed security update guide (Website). The advisory is available at portal.msrc.microsoft.com. The public release was coordinated with the vendor. This vulnerability is handled as CVE-2018-8531. The exploitation is known to be difficult. The attack may be launched remotely. No form of authentication is required for exploitation. The technical details are unknown and an exploit is not available. The structure of the vulnerability defines a possible price range of USD $25k-$100k at the moment (estimation calculated on 10/10/2018). It expected to see the exploit prices for this product increasing in the near future. The advisory points out:

A remote code execution vulnerability exists in the way that Azure IoT Hub Device Client SDK using MQTT protocol accesses objects in memory. The vulnerability could corrupt memory in a way that could allow an attacker to execute arbitrary code in the context of the current user. An attacker who successfully exploited the vulnerability could gain the same user rights as the current user. If the current user is logged on with administrative user rights, the attacker could take control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.

Applying a patch is able to eliminate this problem. A possible mitigation has been published immediately after the disclosure of the vulnerability.

CPE

CVSSv3

VulDB Meta Base Score: 5.0
VulDB Meta Temp Score: 4.8

VulDB Base Score: 5.0
VulDB Temp Score: 4.8
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploiting

Class: Memory corruption (CWE-119)
Local: No
Remote: Yes

Availability: No

Price Prediction: 🔍
Current Price Estimation: 🔒

Threat Intelligence

Threat: 🔍
Adversaries: 🔍
Geopolitics: 🔍
Economy: 🔍
Predictions: 🔍
Actions: 🔍

Countermeasures

Recommended: Patch
Status: Official fix
Reaction Time: 🔒
0-Day Time: 🔒
Exposure Time: 🔒

Timeline

10/09/2018 Advisory disclosed
10/09/2018 Countermeasure disclosed
10/10/2018 VulDB entry created
10/10/2018 VulDB last update

Sources

Advisory: portal.msrc.microsoft.com
Status: Confirmed
Coordinated: 🔒

CVE: CVE-2018-8531 (🔒)

Entry

Created: 10/10/2018
Complete: 🔍

Lien vers l'article source

Auteur: VulDB

Catégories: VulDBNombre de vues: 209

x

Événements SSI