The critical log4j vulnerability, the logging library of the widely used Apache web server, was worldwide in the news. As part of our services make use of Apache web servers, we therefore screened them immediately. The initial conclusion was that the vulnerability is not present in our core services. Because we didn’t enable log4j there.
Afterwards, we looked into third party frameworks that we use. There, we detected the presence of the log4j function in the Elastic Search environment. A popular open source environment for real-time indexing and search. We urgently updated this framework with a log4j patch.
We did this vulnerability sweep on top of our standard security monitoring and maintenance protocol.
Sprint 102 delivered on two fronts that will shape the platform for quarters to come.…
For all the talk about being more connected than ever, a growing share of young…
The US national debt has now crossed the extraordinary threshold of $40 trillion. It doubled in…
Icecat PIM 3.16.0 is here. This Icecat PIM release introduces dedicated Quote Pages, adds batch…
New Mexico is preparing to strengthen its regulation of online platforms following a landmark court…
Artificial intelligence is transforming businesses, attracting enormous investment, and pushing technology stocks to extraordinary valuations.…