| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.0 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in Vavoom. This impacts an unknown function. The manipulation leads to memory corruption. This vulnerability is uniquely identified as CVE-2006-1409. Moreover, an exploit is present.
Details
A vulnerability was found in Vavoom. It has been rated as critical. This issue affects some unknown processing. The manipulation with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to 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. Impacted is availability. The summary by CVE is:
Buffer overflow in Vavoom 1.19.1 and earlier allows remote attackers to cause a denial of service (application crash) via an invalid comprLength value in a compressed packet.
The weakness was disclosed 03/28/2006 by Luigi Auriemma (Website). The advisory is shared at vupen.com. The identification of this vulnerability is CVE-2006-1409 since 03/28/2006. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are unknown but a public exploit is available.
The exploit is available at securityfocus.com. It is declared as proof-of-concept.
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 (25455), SecurityFocus (BID 17261†) and Secunia (SA19388†). The entry VDB-29356 is pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
- 1.1
- 1.3
- 1.4
- 1.4 Beta
- 1.5
- 1.5 Beta
- 1.5.1
- 1.6
- 1.7
- 1.7 Beta 1
- 1.7 Beta 2
- 1.7 Beta 3
- 1.7 Beta 4
- 1.7 Beta 5
- 1.8
- 1.9
- 1.10
- 1.11
- 1.11.1
- 1.11.2
- 1.12
- 1.14
- 1.15
- 1.15 Beta 1
- 1.15.1
- 1.15.2
- 1.15.3
- 1.16
- 1.16.1
- 1.17
- 1.18
- 1.19
- 1.19.1
- 1.666
- 1.666 Beta 1
- 1.666 Beta 2
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.0
VulDB Base Score: 5.3
VulDB Temp Score: 5.0
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: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
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
03/27/2006 🔍03/27/2006 🔍
03/28/2006 🔍
03/28/2006 🔍
03/28/2006 🔍
03/12/2015 🔍
03/26/2019 🔍
Sources
Advisory: vupen.com⛔Researcher: Luigi Auriemma
Status: Not defined
CVE: CVE-2006-1409 (🔍)
GCVE (CVE): GCVE-0-2006-1409
GCVE (VulDB): GCVE-100-29357
X-Force: 25455
SecurityFocus: 17261 - Vavoom Multiple Denial of Service Vulnerabilities
Secunia: 19388 - Vavoom Two Denial of Service Vulnerabilities, Moderately Critical
Vupen: ADV-2006-1104
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 03/12/2015 12:19Updated: 03/26/2019 11:49
Changes: 03/12/2015 12:19 (57), 03/26/2019 11:49 (2)
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.