| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Red-M Red-Alert 2.7.5 V3.1 Build 24. It has been rated as problematic. This issue affects some unknown processing of the component SSID. This manipulation causes denial of service. This vulnerability appears as CVE-2004-2080. There is no available exploit.
Details
A vulnerability was found in Red-M Red-Alert 2.7.5 V3.1 Build 24. It has been declared as problematic. Affected by this vulnerability is an unknown function of the component SSID. The manipulation with an unknown input leads to a denial of service vulnerability. The CWE definition for the vulnerability is CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. As an impact it is known to affect availability. The summary by CVE is:
Red-M Red-Alert 2.7.5 with software 3.1 build 24 converts multiple spaces in a Service Set Identifier (SSID) to a single space, which prevents Red-Alert from correctly identifying the SSID.
The bug was discovered 10/03/2003. The weakness was presented 02/08/2004 by Bruno Morisson (Website). The advisory is shared at securitytracker.com. This vulnerability is known as CVE-2004-2080 since 05/19/2005. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available.
The vulnerability was handled as a non-public zero-day exploit for at least 128 days. During that time the estimated underground price was around $0-$5k.
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 (15089), SecurityFocus (BID 9618†), OSVDB (3953†) and SecurityTracker (ID 1009001†). See VDB-21551 and VDB-21552 for similar entries. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
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: Denial of serviceCWE: CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
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
10/03/2003 🔍02/08/2004 🔍
02/09/2004 🔍
02/09/2004 🔍
02/10/2004 🔍
02/10/2004 🔍
05/19/2005 🔍
10/15/2014 🔍
06/17/2018 🔍
Sources
Advisory: securitytracker.com⛔Researcher: Bruno Morisson
Status: Confirmed
CVE: CVE-2004-2080 (🔍)
GCVE (CVE): GCVE-0-2004-2080
GCVE (VulDB): GCVE-100-21553
X-Force: 15089 - Red-Alert security bypass
SecurityFocus: 9618 - Multiple Red-M Red-Alert Remote Vulnerabilities
OSVDB: 3953 - Red-Alert Multiple Space Character Log Failure
SecurityTracker: 1009001
See also: 🔍
Entry
Created: 10/15/2014 13:56Updated: 06/17/2018 09:53
Changes: 10/15/2014 13:56 (58), 06/17/2018 09:53 (6)
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.