Skip to content
Fencer Vulns
medium 4.6

CVE-2005-0022 json

Buffer overflow in the spa_base64_to_bits function in Exim before 4.43, as originally obtained from Samba code, and as called by the auth_s…

published 2005-01-06 21 y ago modified 2026-06-16 4 mo ago also EUVD-2005-0023

cvss
4.6
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 54%
public exploits
0
none known

Summary

Buffer overflow in the spa_base64_to_bits function in Exim before 4.43, as originally obtained from Samba code, and as called by the auth_spa_client function, may allow attackers to execute arbitrary code during SPA authentication.

Patch / fix

  • exim4 Debian 14, Debian 13, Debian 12 4.34-10

debian advisories DEBIAN-CVE-2005-0022

  • exim RHEL 4 4.43-1.RHEL4.3
  • exim-sa RHEL 4 4.43-1.RHEL4.3
  • exim-mon RHEL 4 4.43-1.RHEL4.3

red hat advisories RHSA-2005:025

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2005-0022 updated

security flaw

  • Red Hat Enterprise Linux AS version 4 exim 4.43-1.RHEL4.3, exim-sa 4.43-1.RHEL4.3, exim-mon 4.43-1.RHEL4.3 Red Hat Enterprise Linux Desktop version 4 exim 4.43-1.RHEL4.3, exim-sa 4.43-1.RHEL4.3, exim-mon 4.43-1.RHEL4.3 Red Hat Enterprise Linux ES version 4 exim 4.43-1.RHEL4.3, exim-sa 4.43-1.RHEL4.3, exim-mon 4.43-1.RHEL4.3 Red Hat Enterprise Linux WS version 4 exim 4.43-1.RHEL4.3, exim-sa 4.43-1.RHEL4.3, exim-mon 4.43-1.RHEL4.3
    fixed: vendor fix RHSA-2005:025

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.72% chance of exploitation in the next 30 days, higher than 54% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 2.0 4.6 AV:L/AC:L/Au:N/C:P/I:P/A:P

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.