Marathon Aleph One up to 0.17.0 Logging logmessagev memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Marathon Aleph One up to 0.17.0 and classified as critical. This affects the function toplevellogger::logmessagev of the component Logging. The manipulation results in memory corruption.
This vulnerability is cataloged as CVE-2006-6664. There is no exploit available.
It is suggested to upgrade the affected component.
Details
A vulnerability was found in Marathon Aleph One up to 0.17.0. It has been classified as critical. Affected is the function toplevellogger::logmessagev of the component Logging. 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:
Format string vulnerability in Marathon Aleph One before 0.17.1 and 2006-12-17 might allow remote attackers to cause a denial of service (application crash) or execute arbitrary code via format string specifiers in the TopLevelLogger::logMessageV function in Misc/Logging.cpp. NOTE: some details were obtained from third party information.
The weakness was shared 12/20/2006 (Website). The advisory is available at vupen.com. This vulnerability is traded as CVE-2006-6664 since 12/20/2006. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Technical details are known, but there is no available exploit.
It is declared as proof-of-concept.
Upgrading to version 0.17.1 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at Secunia (SA23380†). The entry VDB-33953 is related to this item. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 4.8
VulDB Base Score: 5.3
VulDB Temp Score: 4.8
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: Proof-of-Concept
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Marathon Aleph One 0.17.1
Timeline
12/20/2006 🔍12/20/2006 🔍
12/20/2006 🔍
03/12/2015 🔍
03/26/2019 🔍
Sources
Advisory: vupen.com⛔Status: Not defined
Confirmation: 🔍
CVE: CVE-2006-6664 (🔍)
GCVE (CVE): GCVE-0-2006-6664
GCVE (VulDB): GCVE-100-33954
Secunia: 23380
Vupen: ADV-2006-5064
See also: 🔍
Entry
Created: 03/12/2015 22:21Updated: 03/26/2019 15:47
Changes: 03/12/2015 22:21 (48), 03/26/2019 15:47 (4)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.