Libspf2 vulnerabilitiesRanked by how likely they are to be used.
Libspf2 is made by Libspf2 Project. We track 3 published vulnerabilities in it, across 15 versions. None of them is on the list of flaws known to be exploited today. If you run Libspf2, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Libspf2 vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Libspf2's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Libspf2 flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 9.6%CVE-2021-33912Critical
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...
- 9.6%CVE-2021-33913Critical
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,...
- 8.4%CVE-2023-42118High
Exim libspf2 Integer Underflow Remote Code Execution Vulnerability.
Running Libspf2? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
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.
- Matched to
- Libspf2 on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 3 published vulnerabilities listed under the name Libspf2, across 15 versions.
None of Libspf2's vulnerabilities is on the list of flaws known to be exploited today.
Create a EdgeProtect account and track Libspf2. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.