Epic Games Unreal Tournament 3 up to 1.3 ut3mendo.c memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as critical has been found in Epic Games Unreal Tournament 3 up to 1.3. Impacted is an unknown function of the file ut3mendo.c. Such manipulation leads to memory corruption. This vulnerability is documented as CVE-2008-3409. Additionally, an exploit exists.
Details
A vulnerability was found in Epic Games Unreal Tournament 3 up to 1.3 and classified as critical. Affected by this issue is an unknown part of the file ut3mendo.c. 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 confidentiality, integrity, and availability. CVE summarizes:
Buffer overflow in Unreal Tournament 3 1.3beta4 and earlier allows remote attackers to cause a denial of service (memory corruption and daemon crash) or possibly execute arbitrary code via a UDP packet containing a large value in a certain size field, followed by a data string of that size, aka attack 1 in ut3mendo.c.
The weakness was released 07/31/2008 by Luigi Auriemma (Website). The advisory is available at securityfocus.com. This vulnerability is handled as CVE-2008-3409 since 07/31/2008. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. Technical details as well as a public exploit are known.
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 (44105), Exploit-DB (32127), SecurityFocus (BID 30430†) and Secunia (SA31265†). Entry connected to this vulnerability is available at VDB-43467. If you want to get best quality of vulnerability data, you may have to visit VulDB.
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.6
VulDB Base Score: 7.3
VulDB Temp Score: 6.6
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 |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
07/30/2008 🔍07/31/2008 🔍
07/31/2008 🔍
07/31/2008 🔍
03/17/2015 🔍
01/20/2025 🔍
Sources
Advisory: securityfocus.com⛔Researcher: Luigi Auriemma
Status: Not defined
CVE: CVE-2008-3409 (🔍)
GCVE (CVE): GCVE-0-2008-3409
GCVE (VulDB): GCVE-100-43466
X-Force: 44105
SecurityFocus: 30430 - Unreal Tournament 3 Denial Of Service And Memory Corruption Vulnerabilities
Secunia: 31265
Vupen: ADV-2008-2260
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 03/17/2015 12:19Updated: 01/20/2025 18:19
Changes: 03/17/2015 12:19 (57), 03/27/2019 07:40 (1), 01/20/2025 18:19 (21)
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.