| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.8 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Sergey Lyubka Simple HTTPD 1.34. It has been rated as critical. Affected is an unknown function. The manipulation leads to stack-based overflow. This vulnerability is traded as CVE-2006-5216. Furthermore, there is an exploit available. Applying a patch is the recommended action to fix this issue.
Details
A vulnerability was found in Sergey Lyubka Simple HTTPD 1.34 (Web Server). It has been rated as critical. This issue affects an unknown function. The manipulation with an unknown input leads to a stack-based overflow vulnerability. Using CWE to declare the problem leads to CWE-121. A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function). Impacted is confidentiality, integrity, and availability. The summary by CVE is:
Stack-based buffer overflow in Sergey Lyubka Simple HTTPD (shttpd) 1.34 allows remote attackers to execute arbitrary code via a long URI.
The weakness was shared 10/10/2006 by SkOd (Website). The advisory is shared at lists.grok.org.uk. The identification of this vulnerability is CVE-2006-5216 since 10/09/2006. 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 are unknown but a public exploit is available.
The exploit is available at securityfocus.com. It is declared as highly functional.
Applying a patch is able to eliminate this problem.
The vulnerability is also documented in the databases at X-Force (29368), Exploit-DB (2482), SecurityFocus (BID 20393†), Secunia (SA22294†) and SecurityTracker (ID 1017088†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 6.8
VulDB Base Score: 7.3
VulDB Temp Score: 6.8
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: Stack-based overflowCWE: CWE-121 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Highly functional
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
MetaSploit ID: shttpd_post.rb
MetaSploit Name: SHTTPD URI-Encoded POST Request Overflow
MetaSploit File: 🔍
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔍
Timeline
10/06/2006 🔍10/06/2006 🔍
10/09/2006 🔍
10/10/2006 🔍
10/10/2006 🔍
10/19/2006 🔍
03/12/2015 🔍
12/20/2024 🔍
Sources
Advisory: lists.grok.org.ukResearcher: SkOd
Status: Confirmed
CVE: CVE-2006-5216 (🔍)
GCVE (CVE): GCVE-0-2006-5216
GCVE (VulDB): GCVE-100-32669
X-Force: 29368 - Simple HTTPD POST buffer overflow
SecurityFocus: 20393 - SHTTPD Remote Buffer Overflow Vulnerability
Secunia: 22294 - SHTTPD HTTP Request Buffer Overflow Vulnerability, Highly Critical
SecurityTracker: 1017088 - SHTTPD Buffer Overflow Lets Remote Users Execute Arbitrary Code
Vupen: ADV-2006-3939
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/12/2015 15:51Updated: 12/20/2024 13:08
Changes: 03/12/2015 15:51 (69), 09/25/2017 11:30 (2), 07/26/2024 12:32 (17), 12/20/2024 13:08 (6)
Complete: 🔍
Cache ID: 216:576: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.