Disputed code execution via status configuration evaluation
Published Feb 17, 2023 · Updated Mar 18, 2025
The CVE describes code execution in SaltStack Salt 3003 and earlier, allowing remote attackers to abuse the status.custom function. The implementation reads administrator-controlled status keys, extracts the segment after the dot, appends parentheses, and passes the result to Python eval. SUSE classifies the report as invalid because remote attackers cannot influence that configuration-derived input, so the claimed code execution is not reachable through the stated vector.
Summary
What happened
The CVE describes code execution in SaltStack Salt 3003 and earlier, allowing remote attackers to abuse the status.custom function. The implementation reads administrator-controlled status keys, extracts the segment after the dot, appends parentheses, and passes the result to Python eval. SUSE classifies the report as invalid because remote attackers cannot influence that configuration-derived input, so the claimed code execution is not reachable through the stated vector.
The record
- CVE
- CVE-2021-33226
- Published
- Feb 17, 2023
- Updated
- Mar 18, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 17, 2023CVE publishedPublication date reported by the CVE source.
- Mar 18, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo