Incorrect authorization in smart_proxy_salt
Key facts
- Attack vector
- Local
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- None · High · High
- Fix status
- No fix listed
Attack profile from CVSS 3.1 · NVD. Fix status from CNA. Impact type from CWE-863.
Summary
An improper authorization handling flaw was found in Foreman. The Salt plugin for the smart-proxy allows foreman clients to execute actions that should be limited to the Foreman Server. This flaw allows an authenticated local attacker to access and delete limited resources and also causes a denial of service on the Foreman server. The highest threat from this vulnerability is to integrity and system availability.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | smart_proxy_salt | affecting up to, including smart_proxy_salt 2.1.5 | — | No fix listed | CNA |
- smart_proxy_salt Vendor— Affected affecting up to, including smart_proxy_salt 2.1.5 Fixed in — No fix listed CNA
CPE configurations NVD · 1
| CPE | Versions | Role | Vendor |
|---|---|---|---|
| cpe:2.3:a:theforeman:smart_proxy_salt:*:*:*:*:*:foreman:*:* | up to 2.1.5 | Vulnerable | The Foreman Project |
- cpe:2.3:a:theforeman:smart_proxy_salt:*:*:*:*:*:foreman:*:* Versions up to 2.1.5 Vulnerable ·The Foreman Project
Remediation
No fixed version listed by the sources yet.
Vendor assessments
Red Hat
Red Hat rating: Moderate. Red Hat's page for this CVE →
Not affected: 1 product
- Red Hat Satellite 6
Timeline
- 2026-10-02 Threatist record created from CVE-2021-3456
- 2026-10-03 Alias added: GHSA-2j5r-64m5-jpx3
References
Sources
- CVE-2021-3456 · CVE Program
- CVE-2021-3456 · NVD
- FIRST EPSS
- GHSA-2j5r-64m5-jpx3 · GitHub Advisory Database · CC BY 4.0
- CVE-2021-3456 · Red Hat security data · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences