The wsusscn2.cab file has not yet been updated. We will continue to monitor the situation and update this thread periodically until the wsusscn2.cab file has been updated.
Community
Other links
Radia - General Discussions
Patch Tuesday: November 2018
Microsoft has not yet released the November wsusscn2.cab file. As soon as we confirm the latest wsusscn2.cab file has been updated we will update this thread with more details.
Please review the full list of kb numbers below and adjust your acquisition accordingly.
Security Update website:
*For custom bulletin requests please open a case with Accelerite support and provide the kb numbers, OS/ARCHETECTURE(32/64).
Previous 10 comments
The wsusscn2.cab file has not yet been updated. We will continue to monitor the situation and update this thread periodically until the wsusscn2.cab file has been updated.
The wsusscn2.cab file has not yet been updated. We will continue to monitor the situation and update this thread periodically until the wsusscn2.cab file has been updated.
The wsusscn2.cab file has not yet been updated. We will continue to monitor the situation and update this thread periodically until the wsusscn2.cab file has been updated.
The wsusscn2.cab file has not yet been updated. We will continue to monitor the situation and update this thread periodically until the wsusscn2.cab file has been updated
The wusscn2.cab file has been detected. Please start your acquire jobs and let us know if you have any problems.
Hi Jim, wsusscn2.cab file was updated yesterday again. It shrunk slightly. Are you able to identify what they may have changed and if this is an important update to it?
Hi John, I will see if I can find out what has been updated and get back to you.
With testing I confirmed one thing they changed. It seems like they forgot to supersede the September Adobe Flash patch MS-KB4457146 probably because there was no October patch so they missed it. Our devices still showing applicable for the old one even if the November patch MS-KB4467694 is applied. After scanning with the new cab file, it no longer shows applicable. We won't be bothering to deploy the cab file to production for this, we remove the entitlements for the superseded patches so we will just ignore the compliance statistics for that one until next month. Any new builds will get the latest but show vulnerable for the September one. I suppose we could retire it to remove it from the compliance stats.
Hi John,
Thank you for providing those details. I started comparing the differences between the cab files but I was not able to determine what exactly has changed.
Participate
Ask, Discuss, Answer