CVE-2022-22941

An issue was discovered in SaltStack Salt in versions before 3002.8, 3003.4, 3004.1. When configured as a Master-of-Masters, with a publisher_acl, if a user configured in the publisher_acl targets any minion connected to the Syndic, the Salt Master incorrectly interpreted no valid targets as valid, allowing configured users to target any of the minions connected to the syndic with their configured commands. This requires a syndic master combined with publisher_acl configured on the Master-of-Masters, allowing users specified in the publisher_acl to bypass permissions, publishing authorized commands to any configured minion.

A file, directory, or other resource is assigned permissions that allow broader access than intended. Typical impact: unauthorized read, modification, or execution of the resource.

CVE-2022-22941 has a CVSS score of 8.8 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3003.4, 3004.1, 3002.8); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2022-22941? CVE-2022-22941 is a high-severity incorrect permission assignment for critical resource vulnerability in salt (pip), affecting versions >= 3003, < 3003.4. It is fixed in 3003.4, 3004.1, 3002.8. A file, directory, or other resource is assigned permissions that allow broader access than intended.
2. How severe is CVE-2022-22941? CVE-2022-22941 has a CVSS score of 8.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of salt are affected by CVE-2022-22941? salt (pip) versions >= 3003, < 3003.4 is affected.
4. Is there a fix for CVE-2022-22941? Yes. CVE-2022-22941 is fixed in 3003.4, 3004.1, 3002.8. Upgrade to this version or later.
5. Is CVE-2022-22941 exploitable, and should I be worried? Whether CVE-2022-22941 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2022-22941 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2022-22941?
   • Upgrade salt to 3003.4 or later
   • Upgrade salt to 3004.1 or later
   • Upgrade salt to 3002.8 or later