Dibbler 0.6.0 SrvMessages/SrvMsg.cpp tsrvmsg memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in Dibbler 0.6.0. This impacts the function tsrvmsg of the file SrvMessages/SrvMsg.cpp. This manipulation causes memory corruption.
This vulnerability is registered as CVE-2007-5029. No exploit is available.
Details
A vulnerability was found in Dibbler 0.6.0. It has been declared as problematic. Affected by this vulnerability is the function tsrvmsg of the file SrvMessages/SrvMsg.cpp. The manipulation with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect availability. The summary by CVE is:
Dibbler 0.6.0 does not verify that certain length parameters are appropriate for buffer sizes, which allows remote attackers to trigger a buffer over-read and cause a denial of service (daemon crash), as demonstrated by incorrect behavior of the TSrvMsg constructor in SrvMessages/SrvMsg.cpp when (1) reading the option code and option length and (2) parsing options.
The weakness was published 09/18/2007 by Mu Security with Mu Security research team (Website). The advisory is shared at lists.grok.org.uk. This vulnerability is known as CVE-2007-5029 since 09/21/2007. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is 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 SecurityFocus (BID 25726†), OSVDB (40569†) and Secunia (SA26876†). Similar entries are available at VDB-38907 and VDB-38906. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
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: 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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
09/18/2007 🔍09/19/2007 🔍
09/20/2007 🔍
09/21/2007 🔍
09/21/2007 🔍
03/16/2015 🔍
07/29/2021 🔍
Sources
Advisory: lists.grok.org.ukResearcher: Mu Security
Organization: Mu Security research team
Status: Not defined
CVE: CVE-2007-5029 (🔍)
GCVE (CVE): GCVE-0-2007-5029
GCVE (VulDB): GCVE-100-38905
X-Force: 36685
SecurityFocus: 25726 - Dibbler Multiple Memory Corruption Vulnerabilities
Secunia: 26876
OSVDB: 40569 - Dibbler SrvMessages/SrvMsg.cpp TSrvMsg Constructor Remote DoS
See also: 🔍
Entry
Created: 03/16/2015 12:18Updated: 07/29/2021 07:48
Changes: 03/16/2015 12:18 (50), 08/23/2017 11:53 (7), 07/29/2021 07:48 (3)
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.