If you had the misfortune of running a Microsoft Exchange server this past week, then you don’t need me to tell you about the Y2K22 problem. To catch rest of us up, when Exchange tried to download the first malware definitions update of 2022, the version number of the new definitions triggered a crash in the malware detection engine. The date is represented as the string
2201010001
, where the first two digits represent the year. This string gets converted to a signed long integer, which maxes out at 2,147,483,647
. The integer overflows, and the result is undefined behavior, crashing the engine. The server fails safe, not processing any messages without a working malware engine, which means that no e-mail gets through. Happy new year!
More Stories
via Hackaday: Blowing Up Shell Scripts
via Hackaday: Broadcast TV Simulator Keeps the Nostalgia Flowing
via Hackaday: Soldering, Up Close and Personal