cve.bz

CVE-2021-33913 libspf2 project libspf2: Out-of-bounds Write

9.8 criticalExploit referenceEPSS 10%

Critical (9.8) in libspf2 project libspf2. EPSS 10% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
10% (unchanged from 10% a week ago; 9.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 96th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-787 Out-of-bounds Write
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2021-33913 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2021-33913?via=ask-ai-copy and https://cve.bz/cve/CVE-2021-33913?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2021-33913 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
libspf2_project:libspf2before 1.2.11

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian9libspf21.2.10-7+deb9u2DLA-2890-1
Debian12, 13, 14libspf21.2.10-7.1DEBIAN-CVE-2021-33913
Ubuntu20.04:LTSlibspf21.2.10-7+deb9u2build0.20.04.1UBUNTU-CVE-2021-33913 USN-6584-1
UbuntuPro:16.04:LTSlibspf21.2.10-6ubuntu0.1~esm2UBUNTU-CVE-2021-33913 USN-6584-1 USN-6584-2
UbuntuPro:18.04:LTSlibspf21.2.10-7ubuntu0.18.04.1~esm1UBUNTU-CVE-2021-33913 USN-6584-1
Alpinev3.14, v3.15, v3.16 and 8 morelibspf21.2.11-r0ALPINE-CVE-2021-33913

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; the Alpine secdb, CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Alpine.

History

  1. EPSS rose to 10% (10% or more)

Changes since this site first stored the record. The same for every record: /api/public/changes.

References

Check your stackJSON