kajam Gem 1.0.3.rc2 on Ruby MySqlDump Command Line mysql.rb Process information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.5 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in kajam Gem 1.0.3.rc2 on Ruby. This impacts an unknown function in the library vendor/plugins/dataset/lib/dataset/database/mysql.rb of the component MySqlDump Command Line. The manipulation leads to information disclosure (Process). This vulnerability is listed as CVE-2014-4999. The attack must be carried out locally. There is no available exploit.
Details
A vulnerability, which was classified as problematic, has been found in kajam Gem 1.0.3.rc2 on Ruby (Ruby Gem). This issue affects some unknown processing in the library vendor/plugins/dataset/lib/dataset/database/mysql.rb of the component MySqlDump Command Line. The manipulation with an unknown input leads to a information disclosure vulnerability (Process). Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality. The summary by CVE is:
vendor/plugins/dataset/lib/dataset/database/mysql.rb in the kajam gem 1.0.3.rc2 for Ruby places the mysql user password on the (1) mysqldump command line in the capture function and (2) mysql command line in the restore function, which allows local users to obtain sensitive information by listing the process.
The bug was discovered 07/07/2014. The weakness was presented 01/10/2018 (oss-sec). The advisory is shared at openwall.com. The identification of this vulnerability is CVE-2014-4999 since 07/17/2014. An attack has to be approached locally. Required for exploitation is a simple authentication. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
The vulnerability was handled as a non-public zero-day exploit for at least 1283 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.5
VulDB Base Score: 3.3
VulDB Temp Score: 3.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.8
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Name: ProcessClass: Information disclosure / Process
CWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
07/07/2014 🔍07/17/2014 🔍
01/10/2018 🔍
01/10/2018 🔍
01/11/2018 🔍
12/21/2019 🔍
Sources
Advisory: openwall.comStatus: Not defined
CVE: CVE-2014-4999 (🔍)
GCVE (CVE): GCVE-0-2014-4999
GCVE (VulDB): GCVE-100-111593
Entry
Created: 01/11/2018 08:02Updated: 12/21/2019 08:22
Changes: 01/11/2018 08:02 (59), 12/21/2019 08:22 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.