#Windows Protected EAP (PEAP)

**How could an attacker exploit this vulnerability?** An unauthenticated attacker could attack a Microsoft Protected Extensible Authentication Protocol (PEAP) Server by sending specially crafted malicious PEAP packets over the network.

**How could an attacker exploit this vulnerability?** An authenticated attacker could attack a Microsoft Protected Extensible Authentication Protocol (PEAP) Server by sending specially crafted malicious PEAP packets over the network.

**How could an attacker exploit this vulnerability?** An authenticated attacker could attack a Microsoft Protected Extensible Authentication Protocol (PEAP) Server by sending specially crafted malicious PEAP packets over the network.

**How could an attacker exploit this vulnerability?** An unauthenticated attacker could attack a Microsoft Protected Extensible Authentication Protocol (PEAP) Server by sending specially crafted malicious PEAP packets over the network.

**According to the CVSS metric, the attack vector is network (AV:N), and privilege required is low (PR:N), and user interaction is none (UI:N). What is the target used in the context of the remote code execution?** The attacker for this vulnerability could target the server accounts in an arbitrary or remote code execution and attempt to trigger malicious code in the context of the server's account through a network call. The attacker needs no privileges nor does the victim user need to perform and action.

**How could an attacker exploit this vulnerability?** An unauthenticated attacker could attack a Microsoft Protected Extensible Authentication Protocol (PEAP) Server by sending specially crafted malicious PEAP packets over the network.