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

Published on July 23rd, 2019 📆 | 1576 Views ⚑

0

Cherokee Web Server 1.2.103 argv[0] memory corruption


iSpeech.org

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

A vulnerability classified as critical has been found in Cherokee Web Server 1.2.103 (Web Server). This affects an unknown function. The manipulation of the argument argv[0] with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as CWE-119. This is going to have an impact on confidentiality, integrity, and availability.

The weakness was released 07/22/2019. This vulnerability is uniquely identified as CVE-2019-1010218 since 03/20/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/23/2019).

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

Type

Vendor

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 (CWE-119)
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: πŸ”’

03/20/2019 CVE assigned
07/22/2019 +124 days Advisory disclosed
07/23/2019 +1 days VulDB entry created
07/23/2019 +0 days VulDB last update
CVE: CVE-2019-1010218 (πŸ”’)Created: 07/23/2019 06:34 AM
Complete: πŸ”

See the underground prices here!

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

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



Comments are closed.