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 88 is focused on improving story styling control, Amazon synchronization reliability, and a range…
Bruneau, the European leader in office supplies, furniture, and equipment for professionals, is now enriching…
In this sprint, we delivered a set of improvements designed to make Icecat even more…
On 27 January 2026, the European Union and India concluded negotiations on a landmark Free…
In an era where digital shoppers are increasingly wary of "spec-sheet fatigue," the value of…
The revenues of Icecat N.V. (ISIN: NL0012751226) increased slightly during the second half (H2) of…