CVE-2014-4999: vendor/plugins/dataset/lib/dataset/database/mysql.rb in the kajam gem 1.0.3.rc2 for Ruby places the mysql user

This month

HIGH 7.8WATCHLISTDOWNGRADE

CVE-2014-4999 is a high-severity flaw (CVSS 7.8) affecting kajam. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

High severity
Public exploit reference
On your watchlist

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	7.8 (High)
Attack vector	Local
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.5% (top 56%)
CISA exploited list	No
Weakness	CWE-200
Published	2018-01-10
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: kajam project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2018-01-10 18:29 UTCPublished CVE record published
2026-06-17 00:10 UTCUpdated Record last modified

kajam project kajam DOWNGRADE

Affected: 1.0.3 rc2

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.0.3

1. Check installed version

apt-cache policy kajam || rpm -q kajam || kajam --version

2. No fixed release: DOWNGRADE to a release before 1.0.3 (Debian / Ubuntu)

apt-cache madison kajam sudo apt install kajam=<VERSION_BEFORE_1.0.3> sudo apt-mark hold kajam

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list kajam sudo dnf downgrade kajam-<VERSION_BEFORE_1.0.3> sudo dnf versionlock add kajam

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2014-4999?

kajam: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2014-4999 being exploited?

CVE-2014-4999 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2014-4999 affect?

CVE-2014-4999 affects kajam. Severity is high (CVSS 7.8). 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 allo

How urgent is CVE-2014-4999?

Priority 48/100. High severity; Public exploit reference; On your watchlist

Software pages

MySQL vulnerabilities · Ruby vulnerabilities

References

← Back to latest CVEs