Widcomm Bluetooth Connectivity Software 1.3.2.7/1.4.2.10 stack-based overflow
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.1 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in Widcomm Bluetooth Connectivity Software 1.3.2.7/1.4.2.10. This impacts an unknown function. Performing a manipulation results in stack-based overflow. This vulnerability is reported as CVE-2004-0775. No exploit exists.
Details
A vulnerability was found in Widcomm Bluetooth Connectivity Software 1.3.2.7/1.4.2.10. It has been classified as critical. This affects an unknown functionality. The manipulation with an unknown input leads to a stack-based overflow vulnerability. CWE is classifying the issue as CWE-121. A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function). This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Buffer overflow in WIDCOMM Bluetooth Connectivity Software, as used in products such as BTStackServer 1.3.2.7 and 1.4.2.10, Windows XP and Windows 98 with MSI Bluetooth Dongles, and HP IPAQ 5450 running WinCE 3.0, allows remote attackers to execute arbitrary code via certain service requests.
The weakness was disclosed 10/20/2004 by Matt Moore with Pentest Limited (Website). The advisory is shared at pentest.co.uk. This vulnerability is uniquely identified as CVE-2004-0775 since 08/10/2004. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available.
It is declared as functional.
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 databases at X-Force (16953) and SecurityFocus (BID 10914†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.1
VulDB Base Score: 7.3
VulDB Temp Score: 7.1
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: Stack-based overflowCWE: CWE-121 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Functional
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
08/10/2004 🔍08/11/2004 🔍
10/20/2004 🔍
10/20/2004 🔍
01/09/2015 🔍
07/08/2017 🔍
Sources
Advisory: pentest.co.ukResearcher: Matt Moore
Organization: Pentest Limited
Status: Not defined
CVE: CVE-2004-0775 (🔍)
GCVE (CVE): GCVE-0-2004-0775
GCVE (VulDB): GCVE-100-22317
X-Force: 16953 - Bluetooth BTW and BTW-CE/PPC service request buffer overflow
SecurityFocus: 10914 - WIDCOMM Bluetooth Communication Software Multiple Unspecified Buffer Overflow Vulnerabilities
Entry
Created: 01/09/2015 16:10Updated: 07/08/2017 14:18
Changes: 01/09/2015 16:10 (44), 07/08/2017 14:18 (10)
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.