CVE-2025-62348

7.8

Salt Project · Salt

The Salt junos execution module incorrectly handles YAML decoding, which may allow an attacker to achieve code execution under the context of the Salt process.

Executive summary

A critical code injection vulnerability in the Salt junos execution module allows for potential remote code execution under the context of the Salt process.

Vulnerability

The vulnerability is a CWE-94 code injection flaw resulting from unsafe YAML decoding within the junos execution module. The CVSS vector indicates that while the attack requires local access or low-privileged interaction, successful exploitation results in total impact to the confidentiality, integrity, and availability of the Salt process.

Business impact

The ability to execute arbitrary code within the Salt process presents a severe risk to infrastructure management, as Salt is frequently used to manage large-scale server environments. An attacker who exploits this flaw could gain full control over the Salt minion, potentially leading to widespread unauthorized configuration changes, data exfiltration, or total system compromise. With a CVSS score of 7.8, this vulnerability is considered high severity due to the potential for complete control over the affected service.

Remediation

Immediate Action: Upgrade Salt to version 3006.17 or 3007.9, or the latest version provided by your distribution package maintainer, to implement the necessary YAML loader security fix.

Proactive Monitoring: Monitor Salt minion logs for unusual execution patterns or unexpected YAML payloads processed by the junos module.

Compensating Controls: Restrict access to the junos execution module if it is not required for current operations, and ensure that Salt minions are running with the least privilege necessary to perform their tasks.

Exploitation status

Public Exploit Available: No (exploit_available: false)

Analyst recommendation

Given the potential for code execution within the Salt management framework, this vulnerability poses a significant risk to organizational infrastructure. Security teams should prioritize patching affected Salt instances across their environment immediately. If an immediate upgrade is not feasible, ensure that access to the affected module is strictly audited and restricted to prevent the submission of malicious payloads.

Sources

Originally found and disclosed by Amr Kadry, per the CVE Program record.