SaltStack Salt SQL Injection vulnerability in mysql.user_chpass function

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

9.8 · CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS

• CVE-2019-1010259: 1.90% estimated exploitation activity in the next 30 days; percentile 79.68 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

SaltStack Salt 2018.3 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.userchpass function from the MySQL module for Salt (https://github.com/saltstack/salt/blob/develop/salt/modules/mysql.py#L1462). The attack vector is: specially crafted password string. The fixed version is: 2018.3.4.

Published by the source

24 May 2022, 16:50 UTC

Last modified by the source

25 Oct 2024, 20:25 UTC

Source last checked

26 Oct 2026, 13:23 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-h8xp-h3jf-wv4v

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-h8xp-h3jf-wv4v

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2019-1010259

Advisory: SaltStack Salt SQL Injection vulnerability in mysql.user_chpass function
IDs: CVE-2019-1010259, GHSA-h8xp-h3jf-wv4v
Record: https://patchnext.com/advisories/cve-2019-1010259 (revision 2, source checked 26 Oct 2026, 13:23 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: salt 2018.3.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI salt: affected >= 2018.3.0, < 2018.3.4; fixed in 2018.3.4

## Suggested inspection (read-only)
- `python -m pip show salt`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on salt.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-h8xp-h3jf-wv4v (OSV record GHSA-h8xp-h3jf-wv4v lists affected ranges: PyPI salt >=2018.3.0 <2018.3.4 (fixed))
- Verified: https://github.com/advisories/GHSA-h8xp-h3jf-wv4v (GitHub-reviewed advisory GHSA-h8xp-h3jf-wv4v lists affected ranges: PyPI salt >=2018.3.0 <2018.3.4)

Commands are suggestions: review each one before running it.