Frank Yaul corehttp 0.5.3 Alpha http.c HttpSprockMake memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.8 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Frank Yaul corehttp 0.5.3 Alpha and classified as critical. This impacts the function HttpSprockMake of the file http.c. The manipulation leads to memory corruption.
This vulnerability is traded as CVE-2007-4060. Furthermore, there is an exploit available.
Details
A vulnerability was found in Frank Yaul corehttp 0.5.3 Alpha. It has been rated as critical. This issue affects the function HttpSprockMake of the file http.c. The manipulation with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
Multiple buffer overflows in the HttpSprockMake function in http.c in Frank Yaul corehttp 0.5.3alpha allow remote attackers to execute arbitrary code via a long string in the (1) method name or (2) URI in an HTTP request.
The weakness was shared 07/29/2007 by vade79 (Website). The advisory is shared at milw0rm.com. The identification of this vulnerability is CVE-2007-4060 since 07/30/2007. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details as well as a public exploit are known.
A public exploit has been developed in ANSI C. The exploit is available 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 Exploit-DB (4243), SecurityFocus (BID 25120†) and OSVDB (46831†). 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: 8.6VulDB Meta Temp Score: 8.1
VulDB Base Score: 8.6
VulDB Temp Score: 8.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 |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
07/29/2007 🔍07/29/2007 🔍
07/30/2007 🔍
07/30/2007 🔍
07/09/2008 🔍
03/15/2015 🔍
09/29/2024 🔍
Sources
Advisory: milw0rm.com⛔Researcher: vade79
Status: Not defined
CVE: CVE-2007-4060 (🔍)
GCVE (CVE): GCVE-0-2007-4060
GCVE (VulDB): GCVE-100-38069
SecurityFocus: 25120 - CoreHTTP Http.C Buffer Overflow Vulnerability
OSVDB: 46831 - corehttp http.c HttpSprockMake Function Multiple Remote Overflows
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/15/2015 15:58Updated: 09/29/2024 08:05
Changes: 03/15/2015 15:58 (51), 09/06/2018 07:01 (9), 09/29/2024 08:05 (19)
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.