Service crash via malformed SMTP AUTH reply
Published Oct 4, 2025 · Updated Oct 4, 2025
Improper input validation in fetchmail before 6.5.6 allows remote attackers to crash its SMTP client via a malformed 334 AUTH reply. The SMTP_auth routine in smtp.c searches the response for a required space, then increments the null result and passes address 0x1 to the SASL challenge decoder. Exploitation requires configured esmtpname and esmtppassword values with plugout and mda inactive; a crash also terminates daemon mode.
Summary
What happened
Improper input validation in fetchmail before 6.5.6 allows remote attackers to crash its SMTP client via a malformed 334 AUTH reply. The SMTP_auth routine in smtp.c searches the response for a required space, then increments the null result and passes address 0x1 to the SASL challenge decoder. Exploitation requires configured esmtpname and esmtppassword values with plugout and mda inactive; a crash also terminates daemon mode.
The record
- CVE
- CVE-2025-61962
- Published
- Oct 4, 2025
- Updated
- Oct 4, 2025
- Vendor
- fetchmail
- Product
- fetchmail
- Classifications
- CWE-142, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 4, 2025CVE publishedPublication date reported by the CVE source.
- Oct 4, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.9.9 <6.5.6
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo