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 many of the standard operating system services. Attacks that attempt to modify resources other than the small set of resources required by normal service behavior are blocked.
All CSP policies block the standard operating system services 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.
By default the CSP policies allow services read access to most of the file system. To protect against information disclosure vulnerabilities, customers can configure the policy so services cannot even read certain files or folders. This would be appropriate for sensitive areas of the file system that are not normally accessed by the programs and would further limit the damage that information disclosure attacks could cause.
Imported Document Id
This is machine translated content
Login to Subscribe
Please login to set up your subscription.
Didn't find the article you were looking for? Try these resources.