Philips Hue Bridge up to 2.x 1935144020 ZCL String Heap-based memory corruption – Digitalmunition

Exploit/Advisories Cybersecurity study of the dark web exposes vulnerability to machine identities -- ScienceDaily

Published on January 25th, 2020 📆 | 3801 Views ⚑


Philips Hue Bridge up to 2.x 1935144020 ZCL String Heap-based memory corruption

CVSS Meta Temp Score

CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.

Current Exploit Price (≈)

Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.

CTI Interest Score

Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.


A vulnerability was found in Philips Hue Bridge up to 2.x 1935144020. It has been classified as critical. Affected is some unknown functionality of the component ZCL String Handler. The manipulation with an unknown input leads to a memory corruption vulnerability (Heap-based). CWE is classifying the issue as CWE-122. This is going to have an impact on confidentiality, integrity, and availability.

The weakness was presented 01/23/2020. This vulnerability is traded as CVE-2020-6007 since 01/07/2020. It is possible to launch the attack remotely. The technical details are unknown and an exploit is not available. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 01/24/2020).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.



VulDB Meta Base Score: 6.3
VulDB Meta Temp Score: 6.3

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


VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Class: Memory corruption / Heap-based (CWE-122)
Local: No
Remote: Yes

Availability: 🔒
Status: Not defined

Price Prediction: 🔍
Current Price Estimation: 🔒

Threat Intelligenceinfoedit

Threat: 🔍
Adversaries: 🔍
Geopolitics: 🔍
Economy: 🔍
Predictions: 🔍
Remediation: 🔍Recommended: no mitigation known

0-Day Time: 🔒

01/07/2020 CVE assigned
01/23/2020 +16 days Advisory disclosed
01/24/2020 +1 days VulDB entry created
01/24/2020 +0 days VulDB last updateVendor:
CVE: CVE-2020-6007 (🔒)Created: 01/24/2020 09:09 AM
Complete: 🔍


Use the official API to access entries easily!

Tagged with:

Leave a Reply ✍