Pre-auth code execution via flawed EAP bounds check
Published Feb 3, 2020 · Updated Dec 3, 2025
Stack buffer overflow in pppd 2.4.2 through 2.4.8 allows remote attackers to execute arbitrary code through an unsolicited EAP packet. In eap_request and eap_response, an impossible comparison fails to limit the hostname length before copying attacker-controlled bytes into rhostname. Processing occurs before authentication negotiation is accepted, and successful memory corruption can execute code with pppd privileges.
Summary
What happened
Stack buffer overflow in pppd 2.4.2 through 2.4.8 allows remote attackers to execute arbitrary code through an unsolicited EAP packet. In eap_request and eap_response, an impossible comparison fails to limit the hostname length before copying attacker-controlled bytes into rhostname. Processing occurs before authentication negotiation is accepted, and successful memory corruption can execute code with pppd privileges.
The record
- CVE
- CVE-2020-8597
- Published
- Feb 3, 2020
- Updated
- Dec 3, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 3, 2020CVE publishedPublication date reported by the CVE source.
- Dec 3, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- CERT/CC pppd PPTP server proof of conceptproof of concept · unverified
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