Secure Computing Sidewinder G2 6.1.0.01 Monitoring denial of service
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Secure Computing Sidewinder G2 6.1.0.01. It has been classified as problematic. This affects an unknown function of the component Monitoring. Performing a manipulation results in denial of service. This vulnerability is reported as CVE-2004-2545. No exploit exists.
Details
A vulnerability classified as problematic has been found in Secure Computing Sidewinder G2 6.1.0.01. This affects an unknown code block of the component Monitoring. The manipulation with an unknown input leads to a denial of service vulnerability. CWE is classifying the issue as CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. This is going to have an impact on availability. The summary by CVE is:
Secure Computing Corporation Sidewinder G2 6.1.0.01 allows remote attackers to cause a denial of service (SMTP proxy failure) via unknown attack vendors involving an "extremely busy network." NOTE: this might not be a vulnerability because the embedded monitoring sub-system automatically restarts after the failure.
The weakness was disclosed 05/18/2004 (Website). It is possible to read the advisory at securecomputing.com. This vulnerability is uniquely identified as CVE-2004-2545 since 11/20/2005. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. The technical details are unknown and an exploit is not 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 databases at X-Force (16185), SecurityFocus (BID 10373†), OSVDB (6236†) and Secunia (SA11632†). The entries VDB-661, VDB-23290, VDB-23426 and VDB-82020 are pretty similar. Statistical analysis made it clear that VulDB provides the best quality for 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
05/18/2004 🔍05/18/2004 🔍
05/18/2004 🔍
12/31/2004 🔍
11/20/2005 🔍
03/09/2015 🔍
07/19/2017 🔍
Sources
Advisory: securecomputing.comStatus: Not defined
Confirmation: 🔍
CVE: CVE-2004-2545 (🔍)
GCVE (CVE): GCVE-0-2004-2545
GCVE (VulDB): GCVE-100-23427
X-Force: 16185
SecurityFocus: 10373
Secunia: 11632 - Sidewinder G2 Firewall Multiple Denial of Service Vulnerabilities, Moderately Critical
OSVDB: 6236 - Secure Computing Sidewinder G2 Firewall Unspecified SMTP Proxy DoS
See also: 🔍
Entry
Created: 03/09/2015 16:55Updated: 07/19/2017 09:55
Changes: 03/09/2015 16:55 (49), 07/19/2017 09:55 (8)
Complete: 🔍
Cache ID: 216:E38:103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.