CVE-2022-22934
📋 TL;DR
This vulnerability in SaltStack Salt allows attackers to substitute arbitrary pillar data by exploiting the Salt Master's failure to sign pillar data with minion public keys. This affects Salt Masters running versions before 3002.8, 3003.4, or 3004.1, potentially compromising configuration data integrity across managed systems.
💻 Affected Systems
- SaltStack Salt
📦 What is this software?
Salt by Saltstack
Salt by Saltstack
Salt by Saltstack
⚠️ Risk & Real-World Impact
Worst Case
Attackers could inject malicious configuration data into minions, leading to complete system compromise, credential theft, or lateral movement across the infrastructure.
Likely Case
Attackers with network access to Salt Masters could manipulate pillar data to deploy unauthorized configurations, execute arbitrary commands, or steal sensitive data from minions.
If Mitigated
With proper network segmentation and access controls, impact would be limited to isolated segments, though data integrity could still be compromised within those segments.
🎯 Exploit Status
Exploitation requires network access to Salt Master and understanding of Salt's pillar system. No public proof-of-concept has been released, but the vulnerability is well-documented.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: 3002.8, 3003.4, or 3004.1
Vendor Advisory: https://saltproject.io/security_announcements/salt-security-advisory-release/
Restart Required: Yes
Instructions:
1. Identify your Salt version with 'salt --version'. 2. Upgrade to 3002.8, 3003.4, or 3004.1 using your package manager. 3. Restart Salt Master service: 'systemctl restart salt-master'. 4. Verify all minions reconnect properly.
🔧 Temporary Workarounds
Network Segmentation
linuxRestrict network access to Salt Masters to only trusted administrative networks
iptables -A INPUT -p tcp --dport 4505:4506 -s trusted_network -j ACCEPT
iptables -A INPUT -p tcp --dport 4505:4506 -j DROP
🧯 If You Can't Patch
- Implement strict network access controls to limit Salt Master exposure
- Monitor pillar data changes and Salt Master logs for unauthorized modifications
🔍 How to Verify
Check if Vulnerable:
Run 'salt --version' and check if version is below 3002.8, 3003.4, or 3004.1
Check Version:
salt --version
Verify Fix Applied:
After upgrade, verify version is 3002.8, 3003.4, or 3004.1+ and test pillar data signing functionality
📡 Detection & Monitoring
Log Indicators:
- Unauthorized pillar data modifications
- Unexpected minion reconnections
- Salt Master authentication failures
Network Indicators:
- Unusual traffic to Salt Master ports (4505-4506) from unexpected sources
- Pillar data transmission without proper encryption
SIEM Query:
source="salt-master" AND (event="pillar.*modif" OR event="auth.*fail" OR event="unauthorized.*access")
🔗 References
- https://github.com/saltstack/salt/releases%2C
- https://repo.saltproject.io/
- https://saltproject.io/security_announcements/salt-security-advisory-release/%2C
- https://security.gentoo.org/glsa/202310-22
- https://github.com/saltstack/salt/releases%2C
- https://repo.saltproject.io/
- https://saltproject.io/security_announcements/salt-security-advisory-release/%2C
- https://security.gentoo.org/glsa/202310-22