{"id":1425,"date":"2023-02-15T13:19:42","date_gmt":"2023-02-15T18:19:42","guid":{"rendered":"https:\/\/testing.sqalogic.com\/?p=1425"},"modified":"2023-10-25T09:30:23","modified_gmt":"2023-10-25T14:30:23","slug":"vulnerabilite-zero-day-appache-log4j","status":"publish","type":"post","link":"https:\/\/sqalogic.com\/en\/vulnerabilite-zero-day-appache-log4j\/","title":{"rendered":"Zero Day Vulnerability in the Apache log4j"},"content":{"rendered":"<p>As of early December 2021,\u00a0<a href=\"https:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2021-44228\">a critical zero day vulnerability<\/a>\u00a0in the\u00a0<strong>Apache log4j utility<\/strong>\u00a0was published.\u00a0<a href=\"https:\/\/nakedsecurity.sophos.com\/2021\/12\/13\/log4shell-explained-how-it-works-why-you-need-to-know-and-how-to-fix-it\/\">log4shell<\/a>allows arbitrary code execution on affected systems, many of which include servers that are part of the internet\u2019s larger infrastructure and core services.<\/p>\n<p>For our customers concerned about the\u00a0<strong>log4j vulnerability<\/strong>, we understand that the security of your ecosystem is crucial to your success, and that the mission critical roles of those devices mean that any threat is a business critical one. However, with many organizations already in the planning, remediation and\/or monitoring phases, we believe that with the proper strategy, along with the right resources, remediation is quickly attainable.<\/p>\n<p>The\u00a0<strong>log4shell<\/strong>\u00a0exploit leverages a vulnerability in the Java Naming and Directory Interface (JNDI) to perform remote lookups. If an application relies on web servers that are vulnerable to log4shell,\u00a0<strong>log4shell<\/strong>, that application is running on, as the exploitation would occur on the server side (not client).<\/p>\n<p>While it would require significant effort to create an application that uses\u00a0<strong>log4j vulnerability\u00a0<\/strong>you should still practice due diligence and check in with your internal development team and software vendors about their response to log4shell.\u00a0<strong>log4shell<\/strong>If you are experiencing difficulties in contacting your software vendor\u2019s representative, SQALogic can assist our customers in retrieving any information associated with their quality assurance, performance, and general testing software tools.<\/p>\n<p><strong>Here are some of our partners\u2019 remediation recommendations, along with some well-known software industry vendors:<\/strong><\/p>\n<ul>\n<li><a href=\"https:\/\/www.microfocus.com\/en-us\/about\/product-security-response-center\/log4j\">Micro Focus<\/a><\/li>\n<li><a href=\"https:\/\/querysurge.zendesk.com\/hc\/en-us\/articles\/4416702493325-QuerySurge-Patch-Release-Log4j-2-Vulnerability\">RTTS<\/a><\/li>\n<li><a href=\"https:\/\/www.redline13.com\/blog\/2021\/12\/log4j-and-redline13\/\">Redline13<\/a><\/li>\n<li><a href=\"https:\/\/www.ibm.com\/blogs\/psirt\/an-update-on-the-apache-log4j-cve-2021-44228-vulnerability\/\">Worksoft Certify<\/a><\/li>\n<li><a href=\"https:\/\/logging.apache.org\/log4j\/2.x\/\">Apache\/JMeter<\/a><\/li>\n<li><a href=\"https:\/\/guide.blazemeter.com\/hc\/en-us\/articles\/4413675740433-Security-Announcement-Apache-Log4j2-Security-Announcement-Apache-Log4j2\">Blazemeter<\/a><a href=\"https:\/\/github.com\/authomize\/log4j-log4shell-affected\/blob\/main\/affected_apps.md\">GitHub<\/a><\/li>\n<\/ul>\n<p>As part of our own investigation, SQALogic quickly identified and assisted organizations on patching a small number of vulnerable tools within their infrastructures.<\/p>\n<div class=\"entry-content\">\n<p>We will continue to monitor the\u00a0<strong>log4shell<\/strong> situation as it develops.<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>As part of our own investigation, SQALogic quickly identified and assisted organizations on patching a small number of vulnerable tools within their infrastructures.<\/p>","protected":false},"author":1,"featured_media":1427,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[33],"tags":[42,40,41],"class_list":["post-1425","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-nouvelles","tag-appache-log4j","tag-vulnerabilite","tag-zero-day"],"acf":[],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/sqalogic.com\/en\/wp-json\/wp\/v2\/posts\/1425","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sqalogic.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sqalogic.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sqalogic.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/sqalogic.com\/en\/wp-json\/wp\/v2\/comments?post=1425"}],"version-history":[{"count":5,"href":"https:\/\/sqalogic.com\/en\/wp-json\/wp\/v2\/posts\/1425\/revisions"}],"predecessor-version":[{"id":4787,"href":"https:\/\/sqalogic.com\/en\/wp-json\/wp\/v2\/posts\/1425\/revisions\/4787"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/sqalogic.com\/en\/wp-json\/wp\/v2\/media\/1427"}],"wp:attachment":[{"href":"https:\/\/sqalogic.com\/en\/wp-json\/wp\/v2\/media?parent=1425"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sqalogic.com\/en\/wp-json\/wp\/v2\/categories?post=1425"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sqalogic.com\/en\/wp-json\/wp\/v2\/tags?post=1425"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}