CVE-2025-62349: CWE-287 Improper Authentication in Salt Project Salt
Salt contains an authentication protocol version downgrade weakness that can allow a malicious minion to bypass newer authentication/security features by using an older request payload format, enabling minion impersonation and circumventing protections introduced in response to prior issues.
AI Analysis
Technical Summary
CVE-2025-62349 is a vulnerability classified under CWE-287 (Improper Authentication) affecting Salt Project's Salt software, specifically version 3006.12. The issue stems from an authentication protocol version downgrade weakness, where a malicious Salt minion can exploit the system by sending requests formatted according to an older protocol version. This downgrade attack bypasses newer authentication mechanisms and security features that were introduced to mitigate previous vulnerabilities. By doing so, the attacker can impersonate a legitimate minion, gaining unauthorized access to the Salt master’s resources and potentially issuing commands or retrieving sensitive data. The vulnerability requires the attacker to have high privileges on the minion itself, meaning the attacker must already control a minion or have elevated access on it. No user interaction is required for exploitation, and the attack can be performed remotely over the network. The CVSS v3.1 score of 6.2 reflects a medium severity, with high impact on confidentiality and integrity, and low impact on availability. There are no known exploits in the wild at the time of publication, and no patches have been linked yet. This vulnerability highlights the risks of protocol downgrade attacks in distributed orchestration systems and the importance of strict version enforcement in authentication protocols.
Potential Impact
The primary impact of CVE-2025-62349 is the potential for unauthorized access and control within Salt-managed environments. By impersonating a legitimate minion, an attacker can issue unauthorized commands, potentially leading to data exfiltration, unauthorized configuration changes, or lateral movement within an organization's infrastructure. This compromises both the confidentiality and integrity of systems managed by Salt. Although availability impact is low, the breach of trust in the authentication process can undermine the entire security posture of the orchestration environment. Organizations relying heavily on Salt for configuration management, especially in critical infrastructure, cloud environments, and large-scale enterprise deployments, face increased risk of targeted attacks exploiting this vulnerability. The requirement for high privileges on the attacking minion limits the attack surface but does not eliminate risk, especially in environments where minions may be less securely managed or exposed.
Mitigation Recommendations
To mitigate CVE-2025-62349, organizations should: 1) Monitor Salt Project advisories closely and apply patches promptly once available. 2) Restrict and harden access to Salt minions, ensuring that only trusted administrators have high privileges on these nodes. 3) Implement network segmentation and firewall rules to limit communication between minions and the Salt master to trusted sources only. 4) Enable and enforce strict protocol version checks on the Salt master to reject requests using deprecated or older authentication payload formats. 5) Conduct regular audits of Salt minion configurations and logs to detect anomalous authentication attempts or unusual command executions. 6) Employ multi-factor authentication and role-based access controls where possible to reduce the risk of compromised minions. 7) Consider deploying intrusion detection/prevention systems tailored to detect protocol downgrade attempts or unusual Salt traffic patterns. These steps go beyond generic advice by focusing on minimizing the attack surface on minions and enforcing strict protocol compliance.
Affected Countries
United States, Germany, United Kingdom, France, Canada, Australia, Netherlands, Japan, South Korea, India
CVE-2025-62349: CWE-287 Improper Authentication in Salt Project Salt
Description
Salt contains an authentication protocol version downgrade weakness that can allow a malicious minion to bypass newer authentication/security features by using an older request payload format, enabling minion impersonation and circumventing protections introduced in response to prior issues.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2025-62349 is a vulnerability classified under CWE-287 (Improper Authentication) affecting Salt Project's Salt software, specifically version 3006.12. The issue stems from an authentication protocol version downgrade weakness, where a malicious Salt minion can exploit the system by sending requests formatted according to an older protocol version. This downgrade attack bypasses newer authentication mechanisms and security features that were introduced to mitigate previous vulnerabilities. By doing so, the attacker can impersonate a legitimate minion, gaining unauthorized access to the Salt master’s resources and potentially issuing commands or retrieving sensitive data. The vulnerability requires the attacker to have high privileges on the minion itself, meaning the attacker must already control a minion or have elevated access on it. No user interaction is required for exploitation, and the attack can be performed remotely over the network. The CVSS v3.1 score of 6.2 reflects a medium severity, with high impact on confidentiality and integrity, and low impact on availability. There are no known exploits in the wild at the time of publication, and no patches have been linked yet. This vulnerability highlights the risks of protocol downgrade attacks in distributed orchestration systems and the importance of strict version enforcement in authentication protocols.
Potential Impact
The primary impact of CVE-2025-62349 is the potential for unauthorized access and control within Salt-managed environments. By impersonating a legitimate minion, an attacker can issue unauthorized commands, potentially leading to data exfiltration, unauthorized configuration changes, or lateral movement within an organization's infrastructure. This compromises both the confidentiality and integrity of systems managed by Salt. Although availability impact is low, the breach of trust in the authentication process can undermine the entire security posture of the orchestration environment. Organizations relying heavily on Salt for configuration management, especially in critical infrastructure, cloud environments, and large-scale enterprise deployments, face increased risk of targeted attacks exploiting this vulnerability. The requirement for high privileges on the attacking minion limits the attack surface but does not eliminate risk, especially in environments where minions may be less securely managed or exposed.
Mitigation Recommendations
To mitigate CVE-2025-62349, organizations should: 1) Monitor Salt Project advisories closely and apply patches promptly once available. 2) Restrict and harden access to Salt minions, ensuring that only trusted administrators have high privileges on these nodes. 3) Implement network segmentation and firewall rules to limit communication between minions and the Salt master to trusted sources only. 4) Enable and enforce strict protocol version checks on the Salt master to reject requests using deprecated or older authentication payload formats. 5) Conduct regular audits of Salt minion configurations and logs to detect anomalous authentication attempts or unusual command executions. 6) Employ multi-factor authentication and role-based access controls where possible to reduce the risk of compromised minions. 7) Consider deploying intrusion detection/prevention systems tailored to detect protocol downgrade attempts or unusual Salt traffic patterns. These steps go beyond generic advice by focusing on minimizing the attack surface on minions and enforcing strict protocol compliance.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- vmware
- Date Reserved
- 2025-10-10T10:06:33.841Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 697d02b1ac06320222725d79
Added to database: 1/30/2026, 7:12:49 PM
Last enriched: 2/27/2026, 7:33:20 AM
Last updated: 3/25/2026, 2:56:32 AM
Views: 67
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.