Tech-Source Raptor GFX PGX32 2.3.1 Configuration Tool pgxconfig memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.4 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Tech-Source Raptor GFX PGX32 2.3.1 and classified as problematic. This affects an unknown function of the file pgxconfig of the component Configuration Tool. Performing a manipulation results in memory corruption. This vulnerability is reported as CVE-2000-0695. Moreover, an exploit is present.
Details
A vulnerability was found in Tech-Source Raptor GFX PGX32 2.3.1. It has been classified as critical. This affects an unknown part of the file pgxconfig of the component Configuration Tool. 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. The summary by CVE is:
Buffer overflows in pgxconfig in the Raptor GFX configuration tool allow local users to gain privileges via command line options.
The weakness was disclosed 10/20/2000 as not defined posting (Bugtraq). The advisory is shared at archives.neohapsis.com. This vulnerability is uniquely identified as CVE-2000-0695. The exploitability is told to be easy. An attack has to be approached locally. No form of authentication is needed for exploitation. Technical details and a public exploit are known.
The exploit is shared for download at exploit-db.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 vulnerability database at Exploit-DB (20147). The entries VDB-15835 and VDB-15836 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 9.3VulDB Meta Temp Score: 8.4
VulDB Base Score: 9.3
VulDB Temp Score: 8.4
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: Partially
Local: Yes
Remote: No
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
10/20/2000 🔍10/20/2000 🔍
06/27/2014 🔍
01/18/2025 🔍
Sources
Advisory: archives.neohapsis.comStatus: Not defined
CVE: CVE-2000-0695 (🔍)
GCVE (CVE): GCVE-0-2000-0695
GCVE (VulDB): GCVE-100-15837
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 06/27/2014 14:45Updated: 01/18/2025 18:48
Changes: 06/27/2014 14:45 (40), 04/06/2019 00:32 (9), 01/18/2025 18:48 (27)
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.