You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: defender-endpoint/exploit-protection-reference.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -483,7 +483,7 @@ This mitigation protects the following Windows APIs:
483
483
484
484
### Compatibility considerations
485
485
486
-
Legitimate applications that perform API interception may be detected by this mitigation and cause some applications to crash. Examples include security software and application compatibility shims.
486
+
Legitimate applications that perform API interception might be detected by this mitigation and cause some applications to crash. Examples include security software and application compatibility shims.
487
487
488
488
### Configuration options
489
489
@@ -499,7 +499,7 @@ The size of the 32-bit address space places practical constraints on the entropy
499
499
500
500
### Compatibility considerations
501
501
502
-
Most applications that are compatible with Mandatory ASLR (rebasing) are also compatible with the other entropy of Bottom-up ASLR. Some applications may have pointer-truncation issues if they're saving local pointers in 32-bit variables (expecting a base address below 4 GB), and thus will be incompatible with the high entropy option (which can be disabled).
502
+
Most applications that are compatible with Mandatory ASLR (rebasing) are also compatible with the other entropy of Bottom-up ASLR. Some applications might have pointer-truncation issues if they're saving local pointers in 32-bit variables (expecting a base address below 4 GB), and thus will be incompatible with the high entropy option (which can be disabled).
503
503
504
504
### Configuration options
505
505
@@ -636,7 +636,7 @@ If these validations fail, then exception handling is aborted, and the exception
636
636
637
637
### Compatibility considerations
638
638
639
-
Compatibility issues with SEHOP are relatively rare. It's uncommon for an application to take a dependency on corrupting the exception chain. However, some applications are impacted by the subtle changes in timing, which may manifest as a race condition that reveals a latent multi-threading bug in the application.
639
+
Compatibility issues with SEHOP are relatively rare. It's uncommon for an application to take a dependency on corrupting the exception chain. However, some applications are impacted by the subtle changes in timing, which might manifest as a race condition that reveals a latent multi-threading bug in the application.
0 commit comments