Nostromo nhttpd up to 1.9.6 SSL_accept HTTP Request path traversal
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.2 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as problematic has been discovered in Nostromo nhttpd up to 1.9.6. Affected by this issue is the function SSL_accept. Executing a manipulation as part of HTTP Request can lead to path traversal.
This vulnerability is tracked as CVE-2019-16279. The attack can be launched remotely. Moreover, an exploit is present.
Details
A vulnerability classified as problematic was found in Nostromo nhttpd up to 1.9.6 (Web Server). This vulnerability affects the function SSL_accept. The manipulation as part of a HTTP Request leads to a path traversal vulnerability. The CWE definition for the vulnerability is CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. As an impact it is known to affect availability. CVE summarizes:
Directory Traversal in the function SSL_accept in nostromo nhttpd through 1.9.6 allows an attacker to trigger a denial of service via a crafted HTTP request.
The weakness was disclosed 10/14/2019. This vulnerability was named CVE-2019-16279 since 09/13/2019. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Technical details and also a public exploit are known. The MITRE ATT&CK project declares the attack technique as T1006.
A public exploit has been developed by sp0re in Bash and been published immediately after the advisory. It is possible to download the exploit at git.sp0re.sh. 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 entry VDB-143451 is pretty similar. Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.2
VulDB Base Score: 5.3
VulDB Temp Score: 5.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
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: Path traversalCWE: CWE-22
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Author: sp0re
Programming Language: 🔍
Download: 🔍
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: 🔍
Exploit Delay Time: 🔍
Timeline
09/13/2019 🔍10/14/2019 🔍
10/14/2019 🔍
10/15/2019 🔍
01/08/2024 🔍
Sources
Advisory: nazgul.chStatus: Not defined
CVE: CVE-2019-16279 (🔍)
GCVE (CVE): GCVE-0-2019-16279
GCVE (VulDB): GCVE-100-143452
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 10/15/2019 09:23Updated: 01/08/2024 13:42
Changes: 10/15/2019 09:23 (36), 11/10/2019 13:37 (3), 11/10/2019 13:38 (23), 01/08/2024 13:42 (7)
Complete: 🔍
Committer: misc
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.