GoHTTP up to 2017-07-25 scan Long URL memory corruption

A vulnerability was found in GoHTTP up to 2017-07-25. It has been classified as critical. This affects the function scan. The manipulation as part of a Long URL leads to a memory corruption vulnerability (Stack-based). CWE is classifying the issue as CWE-119. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

GoHTTP through 2017-07-25 has a stack-based buffer over-read in the scan function (when called from getRequestType) via a long URL.

The weakness was presented 05/17/2019. This vulnerability is uniquely identified as CVE-2019-12159 since 05/17/2019. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 05/18/2019).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

See 135212 and 135214 for similar entries.

Name

VulDB Meta Base Score: 5.5
VulDB Meta Temp Score: 5.5

VulDB Base Score: ≈5.5
VulDB Temp Score: ≈5.5
VulDB Vector: ?
VulDB Reliability: ?

VulDB Base Score: ?
VulDB Temp Score: ?
VulDB Reliability: ?
Class: Memory corruption / Stack-based (CWE-119)
Local: Yes
Remote: No

Availability: ?
Status: Not defined

Price Prediction: ?
Current Price Estimation: ?

Threat Intelligenceinfoedit

Threat: ?
Adversaries: ?
Geopolitics: ?
Economy: ?
Predictions: ?
Remediation: ?Recommended: no mitigation known
0-Day Time: ?05/17/2019 Advisory disclosed
05/17/2019 +0 days CVE assigned
05/18/2019 +1 days VulDB entry created
05/18/2019 +0 days VulDB last updateCVE: CVE-2019-12159 (?)
See also: ?Created: 05/18/2019 09:28 AM
Complete: ?

Comments are closed.