Bug 1983222 (CVE-2021-32749)
Summary: | CVE-2021-32749 fail2ban: Command injection via mail comand | ||
---|---|---|---|
Product: | [Other] Security Response | Reporter: | Pedro Sampaio <psampaio> |
Component: | vulnerability | Assignee: | Red Hat Product Security <security-response-team> |
Status: | CLOSED UPSTREAM | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | unspecified | CC: | anon.amish, Axel.Thimm, hobbes1069, mjc, orion, tmz, vonsch |
Target Milestone: | --- | Keywords: | Security |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2021-07-16 21:54:51 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1983223, 1983224 | ||
Bug Blocks: |
Description
Pedro Sampaio
2021-07-16 21:18:10 UTC
Created fail2ban tracking bugs for this issue: Affects: epel-all [bug 1983224] Affects: fedora-all [bug 1983223] This CVE Bugzilla entry is for community support informational purposes only as it does not affect a package in a commercially supported Red Hat product. Refer to the dependent bugs for status of those individual community products. Isn't the vulnerability here only present when using the mail command from the mailutils upstream? The mail command in Fedora and EPEL comes from mailx. The upstream fail2ban patches which were applied add `-E 'set escape'` to the mail commands. But the mail command from mailx implements the `-E` option entirely differently. In mailx mail, `-E` takes no arguments; it skips mail which has an empty body. I think the upstream patch breaks any actions which call the mail command in Fedora and EPEL. There is more discussion of this in the upstream issue tracker here: https://github.com/fail2ban/fail2ban/issues/3059 |