| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Epic Games Unreal Tournament 3 and classified as problematic. Affected is an unknown function. Performing a manipulation results in memory corruption. This vulnerability is identified as CVE-2008-7015. Additionally, an exploit exists.
Details
A vulnerability, which was classified as problematic, was found in Epic Games Unreal Tournament 3. This affects an unknown part. 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. The summary by CVE is:
Unreal engine 3, as used in Unreal Tournament 3 1.3, Frontlines: Fuel of War 1.1.1, and other products, allows remote attackers to cause a denial of service (server exit) via a packet with a large length value that triggers a memory allocation failure.
The weakness was released 09/11/2008 by Luigi Auriemma (Website). The advisory is shared at securityfocus.com. This vulnerability is uniquely identified as CVE-2008-7015 since 08/18/2009. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are unknown but a public exploit is available.
The exploit is shared for download 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 (45095), Exploit-DB (32362), SecurityFocus (BID 31140†) and OSVDB (48292†). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
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: 🔍
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
09/11/2008 🔍09/12/2008 🔍
09/20/2008 🔍
08/18/2009 🔍
08/19/2009 🔍
03/18/2015 🔍
01/20/2025 🔍
Sources
Advisory: securityfocus.com⛔Researcher: Luigi Auriemma
Status: Not defined
CVE: CVE-2008-7015 (🔍)
GCVE (CVE): GCVE-0-2008-7015
GCVE (VulDB): GCVE-100-49521
X-Force: 45095 - Unreal Engine memory denial of service
SecurityFocus: 31140 - Unreal Engine Failed Memory Allocation Remote Denial of Service Vulnerability
OSVDB: 48292 - Unreal Engine Packet String Handling Crafted Request Remote DoS
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/18/2015 15:15Updated: 01/20/2025 12:24
Changes: 03/18/2015 15:15 (52), 12/16/2017 07:30 (7), 01/20/2025 12:24 (22)
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.