CVE-2019-1010259: SaltStack Salt 2018.3, 2019.2 is affected by: SQL Injection

This week

CRITICAL 9.8REMOTEDOWNGRADEDOWNGRADE

CVE-2019-1010259 is a critical-severity flaw (CVSS 9.8) affecting salt 2018, salt 2019. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

SaltStack Salt 2018.3, 2019.2 is affected by: SQL Injection. The impact is: An attacker could escalate privileges on MySQL server deployed by cloud provider. It leads to RCE. The component is: The mysql.user_chpass function from the MySQL module for Salt. The attack vector is: specially crafted password string. The fixed version is: 2018.3.4.

Why this priority

Critical severity
Public exploit reference
Remotely exploitable, no login, no user action

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

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.9% (top 20%)
CISA exploited list	No
Weakness	CWE-89
Published	2019-07-18
Last modified	2026-06-17

Publisher (CNA): DWF · Vendor: saltstack

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

Am I affected?

Timeline

2019-07-18 17:15 UTCPublished CVE record published
2026-06-17 02:09 UTCUpdated Record last modified

saltstack salt 2018 DOWNGRADE

Affected: 3.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 3.0

1. Check installed version

apt-cache policy salt-2018 || rpm -q salt-2018 || salt-2018 --version

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

apt-cache madison salt-2018 sudo apt install salt-2018=<VERSION_BEFORE_3.0> sudo apt-mark hold salt-2018

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

dnf --showduplicates list salt-2018 sudo dnf downgrade salt-2018-<VERSION_BEFORE_3.0> sudo dnf versionlock add salt-2018

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.

saltstack salt 2019 DOWNGRADE

Affected: 2.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.0

1. Check installed version

apt-cache policy salt-2019 || rpm -q salt-2019 || salt-2019 --version

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

apt-cache madison salt-2019 sudo apt install salt-2019=<VERSION_BEFORE_2.0> sudo apt-mark hold salt-2019

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

dnf --showduplicates list salt-2019 sudo dnf downgrade salt-2019-<VERSION_BEFORE_2.0> sudo dnf versionlock add salt-2019

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-2019-1010259?

salt 2018: downgrade or apply the listed mitigation; salt 2019: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2019-1010259 being exploited?

CVE-2019-1010259 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-2019-1010259 affect?

CVE-2019-1010259 affects salt 2018, salt 2019. Severity is critical (CVSS 9.8). SaltStack Salt 2018.3, 2019.2 is affected by: SQL Injection. The impact is: An attacker could escalate privileges on MySQL server deployed by cloud provider. It leads to RCE. The component is: The mysql.user_chpass function from the MySQL m

How urgent is CVE-2019-1010259?

Priority 64/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

Software pages

MySQL vulnerabilities

References

← Back to latest CVEs