Y2K22 bug & Log4Shell security vulnerability affect e-mail & server

[Deleted User]

At the beginning of the year, we are still dealing with bugs and security vulnerabilities. The Y2K22 bug is very fresh, causing the Exchange mail delivery to stumble and for which there are only temporary solutions so far. In addition, we take a detailed look at the zero-day security gap Log4Shell, which was too easy to exploit – a brief overview of the most important messages.

On-premises administrators Exchange Server-Systementhat to Turn of the year When they were ready, they were startled at midnight. Because suddenly there were many Exchange servers no mails anymore transport. the Anti-Malware Scan Engine runs when converting the value “2201010001” to a long integer value on a errorso that the process in question can no longer be loaded. At least there is a temporary remedy if the Y2K22 bug stops Exchange mail delivery.

The one that became known in December is more critical than the Y2K22 bug Log4Shell vulnerability. It is one of the most difficult and far-reaching of the last ten years, their concrete scope days and weeks later do not estimate yet leaves. The vulnerability has been around since September 2013 and lies dormant in countless Java apps on servers all over the world. But the security gap Log4Shell: Internet on fire is also in some clients and in network equipment.

Read the full article on the Market Research Telecast blog.