PPTP VPN in Use

A VPN service offers the Point-to-Point Tunneling Protocol (PPTP), whose MS-CHAPv2 authentication can be broken to recover the user's password hash and decrypt the session.

SeverityMedium
CVSS 3.16.5 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N Open in the calculator
CVSS 4.08.3 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N Open in the calculator
CWECWE-327: Use of a Broken or Risky Cryptographic Algorithm
OWASP Top 10A04:2025 Cryptographic Failures
MITRE ATT&CKT1040 Network Sniffing, T1110.002 Password Cracking
CategoryCryptographic Failures

Description

The Point-to-Point Tunneling Protocol (PPTP) is a legacy VPN protocol that uses a control connection on TCP port 1723 and carries traffic in Generic Routing Encapsulation (GRE, IP protocol 47). It normally relies on MS-CHAPv2 to authenticate users, and on Microsoft Point-to-Point Encryption (MPPE), which uses the RC4 stream cipher with keys derived from the MS-CHAPv2 exchange, to protect traffic.

MS-CHAPv2 is fundamentally weak. An attacker who can capture a PPTP authentication exchange, for example on a public Wi-Fi network used by a remote worker or anywhere on the path between client and server, can reduce it to the recovery of a single 56-bit DES key. That key search needs specialised hardware or a cracking service, but it is practical and reveals the user's NT hash regardless of password strength. With the NT hash, the attacker can decrypt the captured VPN traffic, since the MPPE keys derive from it, and then connect to the VPN as that user. MPPE also provides no integrity protection, so traffic can be altered in transit.

Where the VPN account is a domain account, the NT hash can also be used to authenticate to internal services that accept NTLM, which extends the impact beyond the VPN. Microsoft addressed the weakness in a 2012 security advisory, recommending that MS-CHAPv2 be encapsulated in PEAP or that a more secure VPN tunnel be used.

The service is identified by a port scan showing TCP port 1723 open, and confirmed with a PPTP client or Nmap's pptp-version script, which reads details from the server's reply. Vulnerability scanners report it as a PPTP VPN service detected.

Remediation

  • Decommission PPTP and move remote access to a protocol with sound cryptography and mutual authentication, such as IKEv2 with certificate or EAP authentication, or a TLS-based VPN, with multi-factor authentication for users.
  • On Windows Routing and Remote Access, disable the PPTP ports for remote access and demand-dial connections in the port properties; on firewalls and other appliances, disable the PPTP server feature.
  • Close TCP port 1723 and IP protocol 47 (GRE) at the perimeter firewall, unless GRE is needed for another purpose.
  • Treat the passwords of accounts that have connected with PPTP over untrusted networks as exposed, and reset them.

As an interim measure while the migration takes place, limit PPTP to the users who still need it, and require EAP-TLS or PEAP instead of plain MS-CHAPv2 where the clients support it. Confirm the fix by scanning from the internet and checking that TCP port 1723 is closed and no PPTP service answers.

References


Add This Finding to Your Library

In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.

Free trial  ·  No card required

Only need the reporting? Our reporting tool is free and open source, with the same library.


More Network Services Findings

Every Network Services finding