Content in the Patches for Windows site has been modified:
New Fixlets:
[Major] 4077063: Cumulative Update 11 for SQL Server 2014 SP2 - SQL Server 2014 SP2 - KB4077063 (ID: 407706303)
[Major] 4077063: Cumulative Update 11 for SQL Server 2014 SP2 - SQL Server 2014 SP2 - KB4077063 (x64) (ID: 407706301)
[Major] 4077064: Cumulative Update 8 for SQL Server 2016 SP1 - SQL Server 2016 SP1 - KB4077064 (x64) (ID: 407706401)
[Major] 4092643: Cumulative Update 5 for SQL Server 2017 - SQL Server 2017 - KB4092643 (x64) (ID: 409264301)
Modified Fixlets:
[Major] 3125869: Vulnerability in Internet Explorer could lead to ASLR bypass - Disable the User32 Exception Handler Hardening Feature (ID: 1512463)
[Major] 3125869: Vulnerability in Internet Explorer could lead to ASLR bypass - Enable the User32 Exception Handler Hardening Feature (ID: 1512461)
Reason for Update:
Microsoft has released new cumulative updates for SQL servers.
Fixlets for KB3125869 were updated due to potential Relevance false negative.
I am querying as to why it is when ID:1512463 above is rolled out, we then get relevance for ID:1512461, and in turn when this is rolled out, we loop back to receiving relevance for ID:1512463.