Exploit/Advisories Cybersecurity study of the dark web exposes vulnerability to machine identities -- ScienceDaily

Published on July 11th, 2019 📆 | 8172 Views ⚑

0

Mongoose 6.15 mongoose.c mq_parse_http memory corruption


iSpeech

CVSS Meta Temp Score Current Exploit Price (β‰ˆ)
5.5 $0-$5k

A vulnerability was found in Mongoose 6.15. It has been rated as critical. This issue affects the function mq_parse_http of the file mongoose.c. The manipulation with an unknown input leads to a memory corruption vulnerability (Heap-based). Using CWE to declare the problem leads to CWE-122. Impacted is confidentiality, integrity, and availability.

The weakness was shared 07/11/2019. The identification of this vulnerability is CVE-2019-13503 since 07/10/2019. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 07/11/2019).

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

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 / Heap-based (CWE-122)
Local: Yes
Remote: No

Availability: πŸ”’
Status: Not defined





Price Prediction: πŸ”
Current Price Estimation: πŸ”’


0-Day unlock unlock unlock unlock
Today unlock unlock unlock unlock

Threat Intelligenceinfoedit

Threat: πŸ”
Adversaries: πŸ”
Geopolitics: πŸ”
Economy: πŸ”
Predictions: πŸ”
Remediation: πŸ”Recommended: no mitigation known

0-Day Time: πŸ”’

07/10/2019 CVE assigned
07/11/2019 +1 days Advisory disclosed
07/11/2019 +0 days VulDB entry created
07/11/2019 +0 days VulDB last update
CVE: CVE-2019-13503 (πŸ”’)Created: 07/11/2019 12:37 PM
Complete: πŸ”

Download the whitepaper to learn more about our service!

https://vuldb.com/?id.137699

Tagged with: β€’ β€’ β€’



Comments are closed.