“Problems 2000”, also known as Y2K, did not happen on January 1, 2000, but surprisingly struck on January 1, 2022 – at least for MS Exchange users. A bug in the system made mail inaccessible and brought Microsoft’s technical support to its feet.
Problem 2000 was expected to cause computers to crash in early 2000 due to their inability to handle dates made up of so many numbers. Realizing the situation in time, IT professionals around the world worked hard and prepared digital systems so that no problem eventually arose. Mankind has entered the new millennium without a single “exploded” computer.
Now, however, it turns out that the date 01-01-2022 creates a problem in the FIP-FS module of MS Exchange, which protects emails from spam and malware, said DailyMail. A security researcher explained that the defect was caused by a variable named int32 by Microsoft to store the parameters for a date. The maximum value for this int 32 is 2 147 483 647. However, the dates in 2022 start from the value 2 201 010 001. That is why the scanning module “fell”.
As a result of this feature, Microsoft’s scanning software began to accumulate queues of letters and verification messages without being able to deliver them to recipients. This has led to the blocking of servers around the world with the advent of the new year.
The servers began to block in groups, one after the other, according to the time zone in which they are located. System administrators called this Y2K22 after Y2K, the acronym for “Problem 2000.”
As might be expected, the incident started a fire in Microsoft’s technical support department. During this time, system administrators from all over the world began to share on social networks “tricks” to circumvent the problem, including recommendations to disable the scanning module in question. However, security experts have warned that this is not a good idea.