Toshiba Bluetooth wireless device driver up to 3.x Device Driver memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.4 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in Toshiba Bluetooth wireless device driver up to 3.x. Affected by this vulnerability is an unknown functionality of the component Device Driver. This manipulation causes memory corruption. This vulnerability is tracked as CVE-2006-5405. No exploit exists. It is recommended to upgrade the affected component.
Details
A vulnerability was found in Toshiba Bluetooth wireless device driver up to 3.x (Hardware Driver Software). It has been declared as critical. Affected by this vulnerability is some unknown processing of the component Device Driver. The manipulation with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Unspecified vulnerability in Toshiba Bluetooth wireless device driver 3.x and 4 through 4.00.35, as used in multiple products, allows physically proximate attackers to cause a denial of service (crash), corrupt memory, and possibly execute arbitrary code via crafted Bluetooth packets.
The weakness was disclosed 10/18/2006 (Website). The advisory is shared at vupen.com. This vulnerability is known as CVE-2006-5405 since 10/18/2006. The exploitation appears to be difficult. An attack has to be approached locally. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available.
It is declared as proof-of-concept.
Upgrading eliminates this vulnerability.
The vulnerability is also documented in the databases at X-Force (29503), Secunia (SA22402†) and SecurityTracker (ID 1017075†). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 9.3VulDB Meta Temp Score: 8.4
VulDB Base Score: 9.3
VulDB Temp Score: 8.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Proof-of-Concept
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Timeline
10/17/2006 🔍10/18/2006 🔍
10/18/2006 🔍
10/18/2006 🔍
03/12/2015 🔍
04/25/2026 🔍
Sources
Advisory: vupen.com⛔Status: Confirmed
CVE: CVE-2006-5405 (🔍)
GCVE (CVE): GCVE-0-2006-5405
GCVE (VulDB): GCVE-100-32857
X-Force: 29503
Secunia: 22402
SecurityTracker: 1017075
Vupen: ADV-2006-4057
Entry
Created: 03/12/2015 22:21Updated: 04/25/2026 02:01
Changes: 03/12/2015 22:21 (46), 03/26/2019 15:29 (9), 04/25/2026 02:01 (17)
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.