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

Published on July 29th, 2019 📆 | 7453 Views ⚑

0

libslirp 4.0.0 Fragment ip_input.c ip_reass Large Packet memory corruption


iSpeech.org

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

A vulnerability was found in libslirp 4.0.0. It has been rated as critical. This issue affects the function ip_reass of the file ip_input.c of the component Fragment Handler. The manipulation as part of a Large Packet 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 published 07/29/2019. The identification of this vulnerability is CVE-2019-14378 since 07/29/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 07/29/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/29/2019 Advisory disclosed
07/29/2019 +0 days VulDB entry created
07/29/2019 +0 days CVE assigned
07/29/2019 +0 days VulDB last update
CVE: CVE-2019-14378 (πŸ”’)Created: 07/29/2019 03:51 PM
Complete: πŸ”

Download it now for free!

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

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



Comments are closed.