Outgun 1.0/1.0.3/1.0.3 Bot 2 Networking servnet.cpp incoming_client_data memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.9 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in Outgun 1.0/1.0.3/1.0.3 Bot 2. This vulnerability affects the function servernetworking::incoming_client_data of the file servnet.cpp of the component Networking. This manipulation causes memory corruption.
This vulnerability appears as CVE-2006-2399. In addition, an exploit is available.
Details
A vulnerability has been found in Outgun 1.0/1.0.3/1.0.3 Bot 2 and classified as critical. Affected by this vulnerability is the function servernetworking::incoming_client_data of the file servnet.cpp of the component Networking. 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 confidentiality, integrity, and availability. The summary by CVE is:
Stack-based buffer overflow in the ServerNetworking::incoming_client_data function in servnet.cpp in Outgun 1.0.3 bot 2 and earlier allows remote attackers to cause a denial of service (application crash) and possibly execute arbitrary code via a data_file_request command with a long (1) type or (2) name string.
The weakness was presented 05/15/2006 by Luigi Auriemma (Website). The advisory is shared at securityfocus.com. This vulnerability is known as CVE-2006-2399 since 05/15/2006. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details and also a public exploit are known.
It is possible to download the exploit 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 (26509), SecurityFocus (BID 17985†) and Secunia (SA20098†). See VDB-30256, VDB-30255 and VDB-30254 for similar entries. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
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: 🔍
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 |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
05/15/2006 🔍05/15/2006 🔍
05/15/2006 🔍
05/15/2006 🔍
05/15/2006 🔍
03/12/2015 🔍
07/26/2018 🔍
Sources
Advisory: securityfocus.com⛔Researcher: Luigi Auriemma
Status: Not defined
CVE: CVE-2006-2399 (🔍)
GCVE (CVE): GCVE-0-2006-2399
GCVE (VulDB): GCVE-100-30253
X-Force: 26509 - Outgun data_file_request buffer overflow
SecurityFocus: 17985
Secunia: 20098 - Outgun Multiple Vulnerabilities, Highly Critical
Vupen: ADV-2006-1796
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 03/12/2015 12:19Updated: 07/26/2018 14:34
Changes: 03/12/2015 12:19 (61), 07/26/2018 14:34 (2)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.