Point-to-Point Protocol vulnerabilitiesRanked by how likely they are to be used.
Point-to-Point Protocol is made by Point-to-Point Protocol Project. We track 6 published vulnerabilities in it, across 8 versions. None of them is on the list of flaws known to be exploited today. If you run Point-to-Point Protocol, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Point-to-Point Protocol vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Point-to-Point Protocol's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Point-to-Point Protocol flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 20%CVE-2020-8597Critical
eap.c in pppd in ppp 2.4.2 through 2.4.8 has an rhostname buffer overflow in the eap_request and eap_response functions.
- 5.4%CVE-2015-3310Medium
Buffer overflow in the rc_mksid function in plugins/radius/util.c in Paul's PPP Package (ppp) 2.4.6 and earlier, when the PID for pppd is greater than 65535, allows remote attackers to cause a denial of service...
- 3.5%CVE-2014-3158High
Integer overflow in the getword function in options.c in pppd in Paul's PPP Package (ppp) before 2.4.7 allows attackers to "access privileged options" via a long word in an options file, which triggers a heap-based...
- 1.9%CVE-2004-2695High
SQL injection vulnerability in the Authorize.net callback code (subscriptions/authorize.php) in Jelsoft vBulletin 3.0 through 3.0.3 allows remote attackers to execute arbitrary SQL statements via the x_invoice_num...
- 1.9%CVE-2018-11574Critical
Improper input validation together with an integer overflow in the EAP-TLS protocol implementation in PPPD may cause a crash, information disclosure, or authentication bypass.
- 0.4%CVE-2006-2194High
The winbind plugin in pppd for ppp 2.4.4 and earlier does not check the return code from the setuid function call, which might allow local users to gain privileges by causing setuid to fail, such as exceeding PAM...
Running Point-to-Point Protocol? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
eap.c in pppd in ppp 2.4.2 through 2.4.8 has an rhostname buffer overflow in the eap_request and eap_response functions.
- Matched to
- Point-to-Point Protocol on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 6 published vulnerabilities listed under the name Point-to-Point Protocol, across 8 versions.
None of Point-to-Point Protocol's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Point-to-Point Protocol. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.