CVE-2011-1764: Format string vulnerability in the dkim_exim_verify_finish function in src/dkim.c in Exim before 4.76 might allow remote attackers to…
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 3.9% (FIRST EPSS); higher than 90.5% of all records.
- No special conditions are required; it is repeatable.
- Fixed version: exim4 (Debian:12) 4.75-3; exim4 (Debian:6.0) 4.72-6+squeeze1; exim (openSUSE:Tumbleweed) 4.86.2-2.2.
Low priority for now. Upgrade to exim4 (Debian:12) 4.75-3; exim4 (Debian:6.0) 4.72-6+squeeze1; exim (openSUSE:Tumbleweed) 4.86.2-2.2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Format string vulnerability in the dkim_exim_verify_finish function in src/dkim.c in Exim before 4.76 might allow remote attackers to execute arbitrary code or cause a denial of service (daemon crash) via format string specifiers in data used in DKIM logging, as demonstrated by an identity field containing a % (percent) character.
- Published
- Oct 4, 2011
- Updated
- Jun 16, 2026
- EPSS
- 3.9% · 90th percentile
- CWE
- CWE-134
Report tools
Action score
31
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 3.9%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| exim | exim | cpe:2.3:a:exim:exim |
Using exim? Add it to your stack and be the first to know about CVEs like this one. (Email server)
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- exim eximup to 4.75 inclusive
- exim exim2.10
- exim exim2.11
- exim exim2.12
- exim exim3.00
- exim exim3.01
- exim exim3.02
- exim exim3.03
+12 more rows
- exim exim3.10
- exim exim3.11
- exim exim3.12
- exim exim3.13
- exim exim3.14
- exim exim3.15
- exim exim3.16
- exim exim3.20
- exim exim3.21
- exim exim3.22
- exim exim3.30
- exim exim3.31
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | exim4 | before 4.75-3 | 4.75-3 |
| Debian:6.0 | exim4 | before 4.72-6+squeeze1 | 4.72-6+squeeze1 |
| openSUSE:Tumbleweed | exim | before 4.86.2-2.2 | 4.86.2-2.2 |
Same product
exim: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-10149A flaw was found in Exim versions 4.87 to 4.91 (inclusive).KEV99Now
- CVE-2018-6789An issue was discovered in the base64d function in the SMTP listener in Exim before 4.90.1.KEV94Now
- CVE-2010-4344Heap-based buffer overflow in the string_vformat function in string.c in Exim before 4.70 allows remote attackers to execute arbitrary code…KEV91Now
Published before and after this one in the same product
- ← EarlierCVE-2011-0017Feb 1, 2011 · The open_log function in log.c in Exim 4.72 and earlier does not check the return value from (1) setuid or (2) setgid system calls, which…27Monitor
- ← EarlierCVE-2011-1407May 16, 2011 · The DKIM implementation in Exim 4.7x before 4.76 permits matching for DKIM identities to apply to lookup items, instead of only strings…31Monitor
- Later →CVE-2012-5671Oct 31, 2012 · 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…30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:exim4 | 4.75-3 · Debian:12 | Package registry (OSV) |
| opensuse:exim | 4.86.2-2.2 · openSUSE:Tumbleweed | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- P · data can be read
- Integrity
- P · data or configuration can be modified
- Availability
- P · the service can be disrupted
- Attack complexity
- Low
- Confidentiality impact
- P
- Integrity impact
- P
- Availability impact
- P
Weakness class (CWE)
CWE-134 · Use of Externally-Controlled Format StringCVSS vector
AV:N/AC:L/Au:N/C:P/I:P/A:P
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.