Security readout for executives and security teams
Plain-English summary
This CVE reports a critical SaltStack issue in version 3003 and earlier, but the record itself says the claim is disputed because attackers may not control the evaluated input. Business urgency depends on whether your environment runs the named Salt code and whether vendor guidance confirms risk.
Executive priority
Handle as a targeted verification task. The headline CVSS is critical, but the exploitability dispute and missing affected-product metadata mean it should be validated before emergency response decisions.
Technical view
The CVE describes arbitrary code execution through the func variable in salt/modules/status.py and labels it CWE-120 with CVSS 9.8. The affected product metadata is not populated, and the CVE note disputes exploitability because attacker influence over eval input is not established.
Likely exposure
Potentially relevant to organizations running SaltStack/Salt versions described as 3003 or earlier. Exposure cannot be confirmed from the affected-product metadata because it is listed as n/a.
Exploitation context
The source bundle does not show CISA KEV listing or another cited source confirming active exploitation. The CVE is disputed, so exploitation likelihood is unclear from the provided evidence.
Researcher notes
Do not assume confirmed RCE from the CVSS alone. The key question is whether an attacker can influence the func value reaching eval in status.py. Provided sources do not identify a patch, exploit, or confirmed affected CPE.
Mitigation direction
- Inventory SaltStack/Salt deployments and versions.
- Review vendor advisories for CVE-2021-33226 before prioritizing patch work.
- Restrict Salt management interfaces to trusted administrative networks.
- Limit who can invoke Salt modules or submit job functions.
- Monitor Salt project and distribution advisories for clarification.
Validation and detection
- Confirm whether any deployed Salt version is 3003 or earlier.
- Check whether status.py exists in deployed packages.
- Review access controls around Salt job execution.
- Search vendor advisories for a fixed or unaffected version.
- Document whether the disputed eval path is reachable by untrusted users.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-120: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2021-33226 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/saltstack/salt/blob/master/salt/modules/status.pyCVE reference
- https://bugzilla.suse.com/show_bug.cgi?id=1208473CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')
Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.