{"uuid": "b49d4b36-6b85-4673-a1cb-4247b98e5f96", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2021-44228", "type": "exploited", "source": "https://t.me/tech_b0lt_Genona/2965", "content": "\u0412\u0441\u0442\u0440\u0435\u0447\u0430 \u0441 CVE-2021-44228 \u0438\u043c\u0435\u043d\u0438 Log4j2 \u0432 \u043d\u0435\u043e\u0436\u0438\u0434\u0430\u043d\u043d\u043e\u043c \u043c\u0435\u0441\u0442\u0435\n\n> After the initial fix in Log4j v2.15 was released, a new issue CVE-2021-45046 was found and addressed in log4j v2.16. We have since released Arduino IDE 1.8.18, available here, which includes log4j v2.16 with the latest fix.\n\nArduino's response to Log4j2 vulnerability CVE-2021-44228\nhttps://support.arduino.cc/hc/en-us/articles/4412377144338-Arduino-s-response-to-Log4j2-vulnerability-CVE-2021-44228", "creation_timestamp": "2022-01-04T11:40:02.000000Z"}