| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.2 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Omnicron OmniHTTPD 2.0.8. This vulnerability affects unknown code of the component POST Request Handler. Performing a manipulation results in denial of service. This vulnerability is cataloged as CVE-2001-0613. There is no exploit available. It is suggested to use restrictive firewalling.
Details
A vulnerability, which was classified as problematic, was found in Omnicron OmniHTTPD 2.0.8 (Web Server). This affects some unknown functionality of the component POST Request Handler. The manipulation with an unknown input leads to a denial of service vulnerability. CWE is classifying the issue as CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. This is going to have an impact on availability. The summary by CVE is:
Omnicron Technologies OmniHTTPD Professional 2.08 and earlier allows a remote attacker to create a denial of service via a long POST URL request.
The weakness was shared 08/22/2001 (Website). The advisory is shared at archives.neohapsis.com. This vulnerability is uniquely identified as CVE-2001-0613. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available.
The vulnerability scanner Nessus provides a plugin with the ID 15553 (OmniHTTPd Pro Long POST Request DoS), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Web Servers and running in the context r.
It is possible to mitigate the weakness by firewalling .
The vulnerability is also documented in the databases at X-Force (6540), Tenable (15553), SecurityFocus (BID 2730†) and Vulnerability Center (SBV-3245†). 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: 5.3VulDB Meta Temp Score: 5.2
VulDB Base Score: 5.3
VulDB Temp Score: 5.2
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: Denial of serviceCWE: CWE-404
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 |
Nessus ID: 15553
Nessus Name: OmniHTTPd Pro Long POST Request DoS
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
OpenVAS ID: 15553
OpenVAS Name: OmniHTTPd pro long POST DoS
OpenVAS File: 🔍
OpenVAS Family: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: FirewallStatus: 🔍
0-Day Time: 🔍
Timeline
05/15/2001 🔍05/15/2001 🔍
08/22/2001 🔍
08/22/2001 🔍
12/21/2003 🔍
10/25/2004 🔍
07/08/2014 🔍
05/18/2019 🔍
Sources
Advisory: archives.neohapsis.comStatus: Not defined
CVE: CVE-2001-0613 (🔍)
GCVE (CVE): GCVE-0-2001-0613
GCVE (VulDB): GCVE-100-17229
X-Force: 6540
SecurityFocus: 2730 - Omnicron Technologies OmniHTTPd Pro POST DoS Vulnerability
Vulnerability Center: 3245 - OmniHTTPD Professional 2.08 and Earlier DoS via a Long POST URL Request, High
Entry
Created: 07/08/2014 14:52Updated: 05/18/2019 17:27
Changes: 07/08/2014 14:52 (66), 05/18/2019 17:27 (3)
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.