LiveActive security incident?Get immediate response
CVE Record

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

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

SaltStack Salt had a SQL injection flaw in its MySQL password-change helper. In affected deployments, a crafted password value could alter MySQL operations and the CVE states this could escalate privileges and lead to remote code execution. Exposure is narrow but serious where Salt manages MySQL accounts.

Executive priority

Treat as high priority only if Salt manages MySQL users in your environment. The business concern is privilege escalation into database administration and possible RCE, but the source bundle does not establish broad internet exposure or active exploitation.

Technical view

CVE-2019-1010259 affects SaltStack Salt 2018.3 and 2019.2 in mysql.user_chpass within the MySQL module. The vulnerable input is a specially crafted password string. The source bundle names fixed version 2018.3.4, but provides no CVSS, CWE, or vendor advisory details beyond linked code, commit, and PR.

Likely exposure

Likely exposed systems run affected Salt versions and use Salt's MySQL module to change MySQL user passwords. Risk is higher where lower-trust operators, automation, cloud workflows, or external inputs can influence the password value passed into mysql.user_chpass.

Exploitation context

The supplied sources do not show CISA KEV listing or active exploitation. The CVE describes a crafted password string as the attack vector and states impact can include MySQL privilege escalation leading to RCE. Required access path is not fully documented in the bundle.

Researcher notes

Evidence is limited to CVE metadata and upstream code-change references. The affected component and input are clear, but prerequisites, exploit reliability, vulnerable code paths across 2019.2, and downstream package backports require local or vendor confirmation.

Mitigation direction

  • Upgrade affected 2018.3 deployments to fixed version 2018.3.4 or later vendor-supported Salt releases.
  • Check vendor project guidance for the 2019.2 branch before choosing a remediation path.
  • Restrict who can execute Salt MySQL module functions or trigger MySQL password automation.
  • Review automation that passes externally supplied passwords into Salt MySQL user-management functions.

Validation and detection

  • Inventory Salt versions and identify any 2018.3 or 2019.2 installations.
  • Search Salt states, pillars, runners, and orchestration for mysql.user_chpass usage.
  • Confirm whether Salt manages MySQL users on cloud-hosted or managed MySQL services.
  • Review recent MySQL account changes for unexpected privilege grants or anomalous password-change activity.
  • Verify remediation by confirming the deployed Salt package is at a fixed or supported version.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2019-1010259 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
SaltStackSalt2018.3, 2019.2 [fixed: 2018.3.4]Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.