VDB-34201 · CVE-2006-6896 · OSVDB 37586

Plantronic Headset Remote Code Execution

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.
6.3$0-$5k0.00

Summaryinfo

A vulnerability classified as critical has been found in Plantronic Headset. This affects an unknown part. This manipulation causes Remote Code Execution. This vulnerability is handled as CVE-2006-6896. There is not any exploit available.

Detailsinfo

A vulnerability classified as critical was found in Plantronic Headset (version now known). Affected by this vulnerability is some unknown processing. The manipulation with an unknown input leads to a remote code execution vulnerability. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

The Bluetooth stack in the Plantronic Headset does not properly implement Non-pairable mode, which allows remote attackers to conduct unauthorized pair-up operations.

The weakness was released 12/31/2006 as not defined posting (Bugtraq). The advisory is shared at securityfocus.com. This vulnerability is known as CVE-2006-6896 since 01/08/2007. Access to the local network is required for this attack to succeed. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available.

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

The vulnerability is also documented in the vulnerability database at OSVDB (37586†). Entries connected to this vulnerability are available at VDB-34213, VDB-34212, VDB-34211 and VDB-34210. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

Name

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

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: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

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

NVD Base Score: 🔍

Exploitinginfo

Class: Remote Code Execution
CWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Partially

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

12/31/2006 🔍
12/31/2006 +0 days 🔍
01/08/2007 +8 days 🔍
06/26/2007 +169 days 🔍
03/12/2015 +2815 days 🔍
09/29/2017 +932 days 🔍

Sourcesinfo

Advisory: securityfocus.com⛔
Status: Not defined

CVE: CVE-2006-6896 (🔍)
GCVE (CVE): GCVE-0-2006-6896
GCVE (VulDB): GCVE-100-34201
OSVDB: 37586 - Plantronic Headset Bluetooth Non-pairable Mode Unauthorized Remote pair-up Operations

See also: 🔍

Entryinfo

Created: 03/12/2015 22:21
Updated: 09/29/2017 08:57
Changes: 03/12/2015 22:21 (40), 09/29/2017 08:57 (7)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!