exim: Heap-buffer overflow in DNS decode logic used for DKIM
Published Oct 31, 2012
6.8
MEDIUMCVSS 2.0
EPSS 8.38%
Description
Heap-based buffer overflow in the dkim_exim_query_dns_txt function in dkim.c in Exim 4.70 through 4.80, when DKIM support is enabled and acl_smtp_connect and acl_smtp_rcpt are not set to "warn control = dkim_disable_verify," allows remote attackers to execute arbitrary code via an email from a malicious DNS server.
Affected products
No data.
No data.
Red Hat Enterprise Linux 5
exim
Not affected
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 5 | exim | Not affected | n/a |
No package ranges for this CVE.
Remediation
Red Hat statement
Not Vulnerable. This issue does not affect the version of exim as shipped with Red Hat Enterprise Linux 5.
Metrics
No CVSS v4.0 score for this CVE.
No CVSS v3.1 score for this CVE.
No CVSS v3.0 score for this CVE.
AV:N/AC:M/Au:N/C:P/I:P/A:P
This CVE is not in the KEV list.
No CISA SSVC assessment for this CVE yet.
Estimated probability of exploitation in the wild in the next 30 days (FIRST EPSS). As of Oct 1, 2026.
Score over time
2022–2026- EPSS v2
- EPSS v3
- EPSS v4
- EPSS v5
Percentile over time
- EPSS v2
- EPSS v3
- EPSS v4
- EPSS v5
Table of values (17 key points)
Flat stretches are collapsed; showing up to 120 newest points.
| Date | Score | Percentile | Model |
|---|---|---|---|
| Oct 1, 2026 | 8.38% (0.08382) | 94.81th | v5 (v2026.06.15) |
| Jun 15, 2026 | 8.38% (0.08382) | 94.24th | v5 (v2026.06.15) |
| May 13, 2026 | 31.64% (0.31639) | 96.84th | v4 (v2025.03.14) |
| Dec 28, 2025 | 35.73% (0.35729) | 96.92th | v4 (v2025.03.14) |
| Dec 27, 2025 | 10.91% (0.10914) | 93.20th | v4 (v2025.03.14) |
| Oct 28, 2025 | 35.73% (0.35729) | 96.88th | v4 (v2025.03.14) |
| Oct 27, 2025 | 10.91% (0.10914) | 93.10th | v4 (v2025.03.14) |
| Oct 1, 2025 | 35.73% (0.35729) | 96.97th | v4 (v2025.03.14) |
| Jul 30, 2025 | 10.91% (0.10914) | 93.10th | v4 (v2025.03.14) |
| Mar 19, 2025 | 35.73% (0.35729) | 96.59th | v4 (v2025.03.14) |
| Mar 17, 2025 | 32.82% (0.32822) | 96.49th | v4 (v2025.03.14) |
| Dec 12, 2024 | 64.50% (0.64500) | 98.00th | v3 (v2023.03.01) |
| Sep 26, 2024 | 64.50% (0.64500) | 97.94th | v3 (v2023.03.01) |
| Mar 7, 2023 | 70.17% (0.70170) | 97.41th | v3 (v2023.03.01) |
| Mar 6, 2023 | 12.25% (0.12248) | 95.30th | v2 (v2022.01.01) |
| Apr 1, 2022 | 12.25% (0.12248) | 94.93th | v2 (v2022.01.01) |
| Feb 4, 2022 | 12.25% (0.12248) | 89.34th | v2 (v2022.01.01) |
References (19)
- http://lists.fedoraproject.org/pipermail/package-announce/2012-November/091664.html vendor-advisoryx_refsource_FEDORA
- http://lists.fedoraproject.org/pipermail/package-announce/2012-October/090900.html vendor-advisoryx_refsource_FEDORA
- http://lists.fedoraproject.org/pipermail/package-announce/2012-October/090963.html vendor-advisoryx_refsource_FEDORA
- http://lists.opensuse.org/opensuse-security-announce/2012-10/msg00018.html vendor-advisoryx_refsource_SUSE
- http://osvdb.org/86616 vdb-entryx_refsource_OSVDB
- http://secunia.com/advisories/51098 third-party-advisoryx_refsource_SECUNIAVendor Advisory
- http://secunia.com/advisories/51115 third-party-advisoryx_refsource_SECUNIA
- http://secunia.com/advisories/51153 third-party-advisoryx_refsource_SECUNIA
- http://secunia.com/advisories/51155 third-party-advisoryx_refsource_SECUNIA
- http://www.debian.org/security/2012/dsa-2566 vendor-advisoryx_refsource_DEBIAN
- http://www.openwall.com/lists/oss-security/2012/10/26/5 mailing-listx_refsource_MLIST
- http://www.securityfocus.com/bid/56285 vdb-entryx_refsource_BID
- http://www.ubuntu.com/usn/USN-1618-1 vendor-advisoryx_refsource_UBUNTU
- https://access.redhat.com/security/cve/CVE-2012-5671 Vendor Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=869953 Issue Tracking
- https://exchange.xforce.ibmcloud.com/vulnerabilities/79615 vdb-entryx_refsource_XF
- https://lists.exim.org/lurker/message/20121026.080330.74b9147b.en.html mailing-listx_refsource_MLIST
- https://nvd.nist.gov/vuln/detail/CVE-2012-5671
- https://www.cve.org/CVERecord?id=CVE-2012-5671
Change history (0)
No recorded changes yet.