SonicWall has announced that a Y2K22 bug exists in some of its Email Security and Firewall products, causing message log updates and junk box failures since January 1, 2022.
Since January 1, 2022, there has been an issue with SonicWall Email Security products that fail to update junk mailboxes and message logs. Administrators and email users will experience the following two issues.
- Unable to access junk mailbox or unsubscribe from new mail
- Unable to track incoming and outgoing mail by message log
On January 2, SonicWall rolled out an update to North American and European instances of its cloud email security service, Hosted Email Security.
We have also released a fix (Junk Store 7.6.9) for customers using the on-premises Email Security Appliance (ES 10.0.15) and firewalls with the anti-spam Junk Store feature turned on.
In order to upgrade to the latest Junk Store, you need to download and extract the Junk Store 7.6.9 installer (SonicOS 7.x is not affected).
Same bug in Microsoft and Honda
SonicWall did not explain the cause of the Y2K22 bug in their product, but they are not the only company to suffer from this problem.
Starting January 1, owners of Honda and Acura vehicles have reported that the clocks in their in-car navigation systems are automatically set back 20 years to January 1, 2002
Honda and Acura hit by ‘Y2K22’ bug that sends time back to 2002
Reportedly, the Y2K22 bug affects almost all older car models, including Honda’s Pilot, Odyssey, CRV, Ridgeline, Odyssey, and Acura’s MDX, RDX, CSX, and TL.
Microsoft was hit by a similar bug, which caused Microsoft Exchange on-premise servers to stop delivering mail starting January 1, 2022. This is due to the Y2K22 bug affecting the FIP-FS anti-malware scanning engine, causing it to crash when scanning messages.
According to Microsoft, “The version check performed on the signature file causes the malware engine to crash, resulting in the message clogging the transport queue.
Microsoft released a temporary fix on January 5, but is working on an update to automatically address this issue on affected Exchange servers and is seeking further customer response.
Comments