Bug Y2K22 hits Email Security, firewall products

SonicWall: Bug Y2K22 Affects Email Security and Firewall Products

SonicWall today confirmed that some of its email security and firewall products have been affected by bug Y2K22, causing message log updates and spam email failures starting January 1, 2022. .

The company said that mail users and administrators will no longer be able to access the junk mailbox or delete newly received junk mail on the affected systems.

They will also no longer be able to track incoming / outgoing emails using message logs as they are no longer updated.

On January 2, SonicWall rolled out updates to North American and European instances of Hosted Email Security, the company’s cloud-based email security service.

It has also released fixes for its on-premises email security appliance (ES 10.0.15) and customers using firewalls with the Anti-Spam Junk Store feature enabled (Junk Store 7.6.9).

To upgrade to the latest version of the Junk Store, administrators should download and deploy the Junk Store 7.6.9 “installer released under SonicOS 6.5.x firmware in the MySonicWall downloads section for TZ platforms , NSA and SOHO “(SonicOS 7.x is not impacted).

The same bug hit Microsoft and Honda

Even though SonicWall hasn’t explained what is causing bug Y2K22 in its products, they are not the only company affected by this problem.

From January 1, owners of Honda and Acura cars began reporting that the clocks in their on-board navigation systems would automatically be pushed back 20 years, until January 1, 2002.

Reports state that the Y2K22 bug affects almost all older car models, including Honda rider, Odyssey, CRV, Ridgeline, Odyssey and Acura MDX, RDX, CSX and TL.

Microsoft was also affected by the same bug, with on-premises Microsoft Exchange servers stopping email delivery on January 1, 2022, due to the impact of bug Y2K22 on the FIP anti-malware scan engine. -FS, which crashes while scanning messages.

“The version check performed against the signature file causes the malware engine to crash, causing messages to hang in transport queues,” Microsoft explained.

Redmond released an interim fix on January 5, requiring additional customer action while working on an update that would automatically fix the issue on affected Exchange servers.


Please enter your comment!
Please enter your name here

Trending this Week