Bug 2044646 (CVE-2021-33912)

Summary:	CVE-2021-33912 libspf2: Four-byte heap-based buffer overflow in SPF_record_expand_data in spf_expand.c
Product:	[Other] Security Response	Reporter:	Pedro Sampaio <psampaio>
Component:	vulnerability	Assignee:	Red Hat Product Security <security-response-team>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	unspecified	CC:	bojan
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:	2022-01-24 22:30:42 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:	2044647, 2044648
Bug Blocks:

Description Pedro Sampaio 2022-01-24 21:46:28 UTC

libspf2 before 1.2.11 has a four-byte heap-based buffer overflow that might allow remote attackers to execute arbitrary code (via an unauthenticated e-mail message from anywhere on the Internet) with a crafted SPF DNS record, because of incorrect sprintf usage in SPF_record_expand_data in spf_expand.c. The vulnerable code may be part of the supply chain of a site's e-mail infrastructure (e.g., with additional configuration, Exim can use libspf2; the Postfix web site links to unofficial patches for use of libspf2 with Postfix; older versions of spfquery relied on libspf2) but most often is not.

https://github.com/shevek/libspf2/tree/8131fe140704eaae695e76b5cd09e39bd1dd220b
https://nathanielbennett.com/blog/libspf2-cve-jan-2022-disclosure
https://lists.debian.org/debian-lts-announce/2022/01/msg00015.html

Comment 1 Pedro Sampaio 2022-01-24 21:46:45 UTC

Created libspf2 tracking bugs for this issue:

Affects: epel-all [bug 2044648]
Affects: fedora-all [bug 2044647]

Comment 2 Product Security DevOps Team 2022-01-24 22:30:40 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.