libspf2 before 1.2.11 has a four-byte heap-based buffer...
Critical severity
Unreviewed
Published
Jan 20, 2022
to the GitHub Advisory Database
•
Updated Jan 15, 2024
Description
Published by the National Vulnerability Database
Jan 19, 2022
Published to the GitHub Advisory Database
Jan 20, 2022
Last updated
Jan 15, 2024
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.
References