Bug 1993070 (CVE-2021-20314) - CVE-2021-20314 libspf2: stack buffer overflow when processing SPF explanation macros
Summary: CVE-2021-20314 libspf2: stack buffer overflow when processing SPF explanation...
Keywords:
Status: CLOSED UPSTREAM
Alias: CVE-2021-20314
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1993071 1993072
Blocks: 1994465
TreeView+ depends on / blocked
 
Reported: 2021-08-12 10:29 UTC by Dhananjay Arunesh
Modified: 2021-08-17 10:43 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
A stack buffer overflow was found in libspf2 when processing certain SPF macros. This issue can lead to a denial of service and potentially code execution via malicious crafted SPF explanation messages. The highest threat from this vulnerability is to confidentiality, integrity, as well as system availability.
Clone Of:
Environment:
Last Closed: 2021-08-12 13:28:16 UTC
Embargoed:

Attachments (Terms of Use)

Description Dhananjay Arunesh 2021-08-12 10:29:49 UTC 
Stack buffer overflow in libspf2 versions below 1.2.11 when processing certain SPF macros can lead to Denial of service and potentially code execution via malicious crafted SPF explanation messages. CVE-2021-20314 has been assigned to this issue.

References:
https://seclists.org/oss-sec/2021/q3/94
https://github.com/shevek/libspf2/commit/c37b7c13c30e225183899364b9f2efdfa85552ef
Comment 1 Dhananjay Arunesh 2021-08-12 10:30:15 UTC 
Created libspf2 tracking bugs for this issue:

Affects: epel-all [bug 1993072]
Affects: fedora-all [bug 1993071]
Comment 2 Product Security DevOps Team 2021-08-12 13:28:16 UTC 
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.
Note You need to log in before you can comment on or make changes to this bug.