Tuxbr LIBCGI 1.0.2/1.0.3 cgi_lib.c parse_field memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.6 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Tuxbr LIBCGI 1.0.2/1.0.3. It has been classified as critical. Affected by this vulnerability is the function parse_field in the library cgi_lib.c. Performing a manipulation results in memory corruption.
This vulnerability is cataloged as CVE-2002-2257. There is no exploit available.
Details
A vulnerability classified as very critical has been found in Tuxbr LIBCGI 1.0.2/1.0.3. This affects the function parse_field in the library cgi_lib.c. 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:
Stack-based buffer overflow in the parse_field function in cgi_lib.c for LIBCGI 1.0.2 and 1.0.3 allows remote attackers to execute arbitrary code via a long argument.
The weakness was shared 12/31/2002 (Website). It is possible to read the advisory at archives.neohapsis.com. This vulnerability is uniquely identified as CVE-2002-2257 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 of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 06/12/2018).
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 (10722) and SecurityFocus (BID 6270†). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
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.6
VulDB Base Score: 10.0
VulDB Temp Score: 9.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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
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
11/28/2002 🔍12/31/2002 🔍
12/31/2002 🔍
10/14/2007 🔍
08/06/2014 🔍
06/12/2018 🔍
Sources
Advisory: archives.neohapsis.comStatus: Not defined
CVE: CVE-2002-2257 (🔍)
GCVE (CVE): GCVE-0-2002-2257
GCVE (VulDB): GCVE-100-19899
X-Force: 10722 - LIBCGI cgi_lib.c source file parse_field() function buffer overflow
SecurityFocus: 6270 - TuxBR LIGCGI Buffer Overflow Vulnerability
Entry
Created: 08/06/2014 18:25Updated: 06/12/2018 10:52
Changes: 08/06/2014 18:25 (52), 06/12/2018 10:52 (2)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.