SCSPBP3: IIS Protection
The out-of-the-box CSP policies provide significant protection against these attacks. No policy updates are necessary. As soon as the injected code attempts behavior that is not normal for the program it was injected into, CSP blocks that behavior. Since the goal of most attacks is to use the program's privileges in unauthorized ways, most attacks will be blocked. Some specific examples:
- All CSP policies provide tight confinement around the IIS service. Attacks that attempt to modify resources other than the small set of resources required by normal IIS service behavior are blocked.
- All CSP policies block the IIS service from launching suspicious programs. So if the attack code tries to download and run a Trojan program, it won't be able to launch the Trojan. This is true whether the attack is made via this vulnerability or any other method.
- All CSP policies block incoming network connections by default, thus preventing access to this vulnerability from remote systems. If inbound network connections are required, the customer must configure the policy to allow specific remote networks to connect. Unknown (and potentially malicious) remote systems would still be blocked.
- IIS worker processes (w3wp) are confined by the Generic Windows Service Protection. These are somewhat less restrictive than the IIS-specific confinement because the work processes execute arbitrary application code and not IIS-specific code.
Rate this Article