CVE-2021-3457 json
An improper authorization handling flaw was found in Foreman.
published 2021-05-12 5 y ago modified 2026-06-17 4 mo ago also EUVD-2021-26780
- cvss
- 6.1
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 15%
- public exploits
- 0
- none known
Summary
An improper authorization handling flaw was found in Foreman. The Shellhooks 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.
Patch / fix
- theforeman smart_proxy_shell_hooks 0.9.2
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2021-3457 updated cvss 6.1
smart_proxy_shellhooks: unauthorized users can execute actions that should be reserved for foreman
-
Red Hat Satellite 6 smart_proxy_shellhooksnot affected: vulnerable code not present “To mitigate the flaw, disable the smart_proxy_shellhooks plugin from the Server.”
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.24% chance of exploitation in the next 30 days, higher than 15% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 6.1 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H |
| NVD | 2.0 | 3.6 | AV:L/AC:L/Au:N/C:N/I:P/A:P |
Affected products
- n/a smart_proxy_shellhooks
Classification
- Weakness
-
- CWE-863 Incorrect Authorization
References
-
bugzilla.redhat.com
/show_bug.cgi?id=1940990
issue-tracking, third-party-advisory
Sources
- CVE List CVE-2021-3457
- NVD CVE-2021-3457
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.