| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.6 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Valve Half-Life 1.1.1.0 on Dedicated Server. The impacted element is an unknown function. This manipulation causes memory corruption. Remote exploitation of the attack is possible. Furthermore, an exploit is available. It is advisable to implement restrictive firewalling.
Details
A vulnerability was found in Valve Half-Life 1.1.1.0 on Dedicated Server. It has been declared as problematic. Affected by this vulnerability is some unknown functionality. 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 weakness was published 07/29/2003 by Auriemma Luigi with PivX Solutions (Website). The advisory is shared at pivx.com. The attack can be launched remotely. Technical details are unknown but an exploit is available.
An exploit has been developed in ZIP Archive. It is possible to download the exploit at pivx.com. It is declared as proof-of-concept. We expect the 0-day to have been worth approximately $5k-$25k.
Applying a patch is able to eliminate this problem. The bugfix is ready for download at pivx.com.Proper firewalling of is able to address this issue. The best possible mitigation is suggested to be applying a restrictive firewalling.
Similar entries are available at VDB-207 and VDB-206. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.0VulDB Meta Temp Score: 4.6
VulDB Base Score: 5.0
VulDB Temp Score: 4.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: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Proof-of-Concept
Programming Language: 🔍
Download: 🔍
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: FirewallStatus: 🔍
0-Day Time: 🔍
Patch: pivx.com
Timeline
07/29/2003 🔍07/30/2003 🔍
06/26/2019 🔍
Sources
Advisory: pivx.comResearcher: Auriemma Luigi
Organization: PivX Solutions
Status: Not defined
GCVE (VulDB): GCVE-100-205
See also: 🔍
Entry
Created: 07/30/2003 18:14Updated: 06/26/2019 10:08
Changes: 07/30/2003 18:14 (52), 06/26/2019 10:08 (1)
Complete: 🔍
Cache ID: 216:C4A: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.