CVE-2021-33913
Libspf2 Project Libspf2 vulnerability
libspf2 before 1.2.11 has a 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 SPF_record_expand_data in spf_expand.c. The amount of overflowed data depends on the relationship between the length of an entire domain name and the length of its leftmost label. 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.
High priority: this vulnerability is rated critical and can be attacked over the network without a login.
Affected products
Libspf2. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Libspf2 Project Libspf2 runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/shevek/libspf2/tree/8131fe140704eaae695e76b5cd09e39bd1dd220b · Third Party Advisory
- lists.debian.org/debian-lts-announce/2022/01/msg00015.html · Third Party Advisory
- nathanielbennett.com/blog/libspf2-cve-jan-2022-disclosure · Exploit
- security.gentoo.org/glsa/202401-22
- nvd.nist.gov/vuln/detail/CVE-2021-33913
- cve.org/CVERecord?id=CVE-2021-33913
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.