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

Published on October 2nd, 2019 📆 | 7575 Views ⚑

0

Elastic Code 7.3.0/7.3.1/7.3.2 Repository Import information disclosure


iSpeech

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

A vulnerability has been found in Elastic Code 7.3.0/7.3.1/7.3.2 and classified as problematic. Affected by this vulnerability is an unknown function of the component Repository Import Handler. The manipulation with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. As an impact it is known to affect confidentiality.

The weakness was disclosed 10/01/2019. This vulnerability is known as CVE-2019-7618 since 02/07/2019. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 10/02/2019).

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

Vendor

Name

VulDB Meta Base Score: 3.5
VulDB Meta Temp Score: 3.5

VulDB Base Score: β‰ˆ3.5
VulDB Temp Score: β‰ˆ3.5
VulDB Vector: πŸ”’
VulDB Reliability: πŸ”

VulDB Base Score: πŸ”’
VulDB Temp Score: πŸ”’
VulDB Reliability: πŸ”
Class: Information disclosure (CWE-200)
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: πŸ”’

02/07/2019 CVE assigned
10/01/2019 +236 days Advisory disclosed
10/02/2019 +1 days VulDB entry created
10/02/2019 +0 days VulDB last update
CVE: CVE-2019-7618 (πŸ”’)Created: 10/02/2019 08:31 AM
Complete: πŸ”

See the underground prices here!

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

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



Comments are closed.