Marcos Luiz Onisto Lib CGI 0.1 libcgi.h changevalue memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.1 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in Marcos Luiz Onisto Lib CGI 0.1. Impacted is the function changevalue in the library libcgi.h. Performing a manipulation results in memory corruption.
This vulnerability was named CVE-2002-2251. In addition, an exploit is available.
Details
A vulnerability, which was classified as critical, was found in Marcos Luiz Onisto Lib CGI 0.1. This affects the function changevalue in the library libcgi.h. 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 overflow in the changevalue function in libcgi.h for Marcos Luiz Onisto Lib CGI 0.1 allows remote attackers to execute arbitrary code via a long argument.
The weakness was presented 12/31/2002 (Website). The advisory is shared at archives.neohapsis.com. This vulnerability is uniquely identified as CVE-2002-2251 since 10/14/2007. 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 and a public exploit are known.
A public exploit has been developed in ANSI C. The exploit is shared for download at securityfocus.com. It is declared as proof-of-concept. The commercial vulnerability scanner Qualys is able to test this issue with plugin 10918 (Lib CGI Include Buffer Overflow Vulnerability).
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 (10715), Exploit-DB (22049) and SecurityFocus (BID 6264†). 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: 10.0VulDB Meta Temp Score: 9.1
VulDB Base Score: 10.0
VulDB Temp Score: 9.1
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
Programming Language: 🔍
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Qualys ID: 🔍
Qualys Name: 🔍
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
11/27/2002 🔍12/31/2002 🔍
12/31/2002 🔍
10/14/2007 🔍
08/06/2014 🔍
08/29/2025 🔍
Sources
Advisory: archives.neohapsis.comStatus: Not defined
CVE: CVE-2002-2251 (🔍)
GCVE (CVE): GCVE-0-2002-2251
GCVE (VulDB): GCVE-100-19893
X-Force: 10715 - LIB CGI libcgi.h file \
SecurityFocus: 6264 - Lib CGI Include Buffer Overflow Vulnerability
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 08/06/2014 18:23Updated: 08/29/2025 05:50
Changes: 08/06/2014 18:23 (51), 04/20/2019 11:39 (7), 03/18/2025 14:24 (16), 08/29/2025 05:50 (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.