Jason Boettcher Liero Xtreme up to 0.62b visualization memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.9 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical was found in Jason Boettcher Liero Xtreme up to 0.62b. This affects the function visualization. The manipulation results in memory corruption.
This vulnerability is cataloged as CVE-2006-1075. There is no exploit available.
Details
A vulnerability, which was classified as critical, was found in Jason Boettcher Liero Xtreme up to 0.62b. Affected is the function visualization. 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 confidentiality, integrity, and availability. CVE summarizes:
Format string vulnerability in the visualization function in Jason Boettcher Liero Xtreme 0.62b and earlier allows remote attackers to execute arbitrary code via format string specifiers in (1) a nickname, (2) a dedicated server name, or (3) a mapname in a level (aka .lxl) file.
The weakness was shared 03/08/2006 by Luigi Auriemma (Website). The advisory is shared for download at vupen.com. This vulnerability is traded as CVE-2006-1075 since 03/08/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. There are known technical details, but no exploit is available.
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 (25187), SecurityFocus (BID 16990†) and Secunia (SA19079†). The entry VDB-29063 is related to this item. VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 6.9
VulDB Base Score: 7.3
VulDB Temp Score: 6.9
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
03/06/2006 🔍03/08/2006 🔍
03/08/2006 🔍
03/08/2006 🔍
03/08/2006 🔍
03/12/2015 🔍
09/07/2017 🔍
Sources
Advisory: vupen.com⛔Researcher: Luigi Auriemma
Status: Not defined
CVE: CVE-2006-1075 (🔍)
GCVE (CVE): GCVE-0-2006-1075
GCVE (VulDB): GCVE-100-29064
X-Force: 25187 - Liero Xtreme visualization function format string
SecurityFocus: 16990 - Liero Xtreme Remote Format String Vulnerability
Secunia: 19079 - Liero Xtreme Format String and Denial of Service Vulnerabilities, Highly Critical
Vupen: ADV-2006-0849
See also: 🔍
Entry
Created: 03/12/2015 12:19Updated: 09/07/2017 09:21
Changes: 03/12/2015 12:19 (53), 09/07/2017 09:21 (7)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.