| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.2 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as critical has been found in VooDoo cIRCle up to 1.0.32. This affects an unknown part. The manipulation results in memory corruption. This vulnerability is reported as CVE-2005-1326. No exploit exists. Further authentication should be added.
Details
A vulnerability was found in VooDoo cIRCle up to 1.0.32 (Customer Relationship Management System). It has been classified as critical. Affected is an unknown part. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as 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. This is going to have an impact on availability. CVE summarizes:
Buffer overflow in VooDoo cIRCle BOTNET before 1.0.33 allows remote authenticated attackers to cause a denial of service (client crash) via a crafted packet.
The weakness was disclosed 04/25/2005 (Website). The advisory is shared for download at sourceforge.net. This vulnerability is traded as CVE-2005-1326 since 04/27/2005. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. There are neither technical details nor an exploit publicly available.
Upgrading to version 1.0.33 eliminates this vulnerability. It is possible to mitigate the problem by adding an authentication mechanism. The best possible mitigation is suggested to be adding authentication.
The vulnerability is also documented in the databases at X-Force (20273), SecurityFocus (BID 13394†), OSVDB (15830†) and Secunia (SA15110†). Once again VulDB remains the best source for vulnerability data.
Product
Type
Name
Version
- 1.0.0
- 1.0.1
- 1.0.2
- 1.0.3
- 1.0.4
- 1.0.5
- 1.0.6
- 1.0.7
- 1.0.8
- 1.0.9
- 1.0.10
- 1.0.11
- 1.0.12
- 1.0.13
- 1.0.14
- 1.0.15
- 1.0.16
- 1.0.17
- 1.0.18
- 1.0.19
- 1.0.20
- 1.0.21
- 1.0.22
- 1.0.23
- 1.0.24
- 1.0.25
- 1.0.26
- 1.0.27
- 1.0.28
- 1.0.29
- 1.0.30
- 1.0.31
- 1.0.32
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.2
VulDB Base Score: 5.3
VulDB Temp Score: 5.2
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: 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: AuthenticationStatus: 🔍
0-Day Time: 🔍
Upgrade: VooDoo cIRCle 1.0.33
Timeline
04/25/2005 🔍04/26/2005 🔍
04/26/2005 🔍
04/26/2005 🔍
04/27/2005 🔍
05/02/2005 🔍
03/11/2015 🔍
03/26/2019 🔍
Sources
Advisory: sourceforge.netStatus: Not defined
Confirmation: 🔍
CVE: CVE-2005-1326 (🔍)
GCVE (CVE): GCVE-0-2005-1326
GCVE (VulDB): GCVE-100-24972
X-Force: 20273
SecurityFocus: 13394 - VooDoo Circle BotNet Connection Denial of Service Vulnerability
Secunia: 15110 - VooDoo cIRCle BOTNET Buffer Overflow Vulnerability, Less Critical
OSVDB: 15830 - VooDoo cIRCle BOTNET Remote Overflow
Entry
Created: 03/11/2015 11:41Updated: 03/26/2019 09:15
Changes: 03/11/2015 11:41 (59), 03/26/2019 09:15 (1)
Complete: 🔍
Cache ID: 216:53D:103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.