"Put simply, a bug subsequently dubbed #Y2K22 (named in the style of the Y2K bug that spooked the world starting about a quarter century ago) caused the software to be unable to handle the date format for the year 2022. #Microsoft ’s fix? Set the date on malware detection updates back to the fictional December 33rd, 2021" https://www.welivesecurity.com/2022/02/21/integer-overflow-how-it-occur-can-be-prevented/
#y2k22
#Y2k22 bug is causing #Microsoft #Exchange #Server to #fail worldwide: FIP-FS Scan Engine failed to load
source: https://mspoweruser.com/y2k22-bug-is-causing-microsoft-exchange-server-to-fail-worldwide/
The issue appears to be due to Microsoft using the first two numbers of the #update #version to denote the year of the update, which caused the “long” version of the date to #overflow.
1 Comments
2 Shares