Re: [PLUG] Microsoft Exchange year 2022 bug in FIP-FS breaks email delivery

[Walt Mankowski via plug <plug@lists.phillylinux.org>]

Arstechnica had a report on this bug yesterday, and it's an even worse
bug than the original report made it seem. Turns out that 32-bit
number wasn't being used for the date, but as a version number where
the first 2 digits were the year! And they pushed it out on New Year's Eve!

https://arstechnica.com/information-technology/2022/01/exchange-server-bug-gets-a-fix-after-ruining-admins-new-years-plans/

On Sun, Jan 02, 2022 at 06:10:24AM -0500, Walt Mankowski via plug wrote:
> Hi everyone,
> 
> I just read about this on my work Slack. I know there are some Microsoft admins on the list so I thought I'd pass it along. And for everyone else, well, it's just a bizarre bug.
> 
> Exchange's spam and malware checking engine was storing dates in a signed 32-bit integer. The date value for 2022-01-01 is 2,201,010,001. Since this is bigger than 2^31 = 2,147,483,648, this prevented mail from being delivered. You can read more at https://www.bleepingcomputer.com/news/microsoft/microsoft-exchange-year-2022-bug-in-fip-fs-breaks-email-delivery/.
> 
> Microsoft posted a fix late last night at https://techcommunity.microsoft.com/t5/exchange-team-blog/email-stuck-in-transport-queues/ba-p/3049447.
> 
> Walt

> ___________________________________________________________________________
> Philadelphia Linux Users Group         --        http://www.phillylinux.org
> Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
> General Discussion  --   http://lists.phillylinux.org/mailman/listinfo/plug

Attachment: signature.asc
Description: PGP signature

___________________________________________________________________________
Philadelphia Linux Users Group         --        http://www.phillylinux.org
Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
General Discussion  --   http://lists.phillylinux.org/mailman/listinfo/plug