{"uuid": "7483351d-3dca-4d98-a969-be9fd342e07b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-44228", "type": "seen", "source": "https://t.me/hacking_Attack/36752", "content": "Black Hat Ethical Hacking\nLog4j 2.17.1 out now, fixes new remote code execution bug\n\nhttps://www.blackhatethicalhacking.com/wp-content/uploads/2021/08/Untitled-design-2-1.png Log4j 2.17.1 out now, fixes new remote code execution bugPost Views: 200 https://www.blackhatethicalhacking.com/wp-content/uploads/2021/08/BECOME-A-PATRON-AND-UNLOCK-EXCLUSIVE-VIDEOS-1.png Reading Time: 1 Minute\nApache has released another Log4j version, 2.17.1 fixing a newly discovered remote code execution (RCE) vulnerability in 2.17.0, tracked as CVE-2021-44832.\nPrior to today, 2.17.0 was the most recent version of Log4j and deemed the safest release to upgrade to, but that advice has now evolved. Fifth Log4j CVE in under\u00a0a monthMass\u00a0exploitation of the original Log4Shell vulnerability\u00a0(CVE-2021-44228) by threat actors began around December 9th, when a PoC exploit\u00a0for it surfaced on GitHub.\n\nGiven Log4j\u2019s vast usage\u00a0in the majority of Java applications, Log4Shell soon\u00a0turned into a nightmare for enterprises and governments\u00a0worldwide.\n\nWhile the critical risk posed by the original Log4Shell exploit is\u00a0paramount, milder variants of the vulnerability\u00a0emerged in Log4j versions, including 2.15 and 2.16\u2014previously believed to be fully patched.\n\nBleepingComputer earlier reported on four different\u00a0CVEs impacting Log4j\u00a0and one discovered in the \u2018logback\u2019 framework.\u00a0After the discovery of a DoS flaw\u00a0in version 2.16, the advice had swiftly shifted towards upgrading to version 2.17.0, deemed the safest of all.\n\nBut now a fifth vulnerability\u2014an RCE flaw, tracked as CVE-2021-44832 has been discovered in 2.17.0, with a patch applied to the newest\u00a0release 2.17.1\u00a0which is out.\n\nRated \u2018Moderate\u2019 in severity and assigned a 6.6 score on the CVSS scale, the vulnerability stems from the lack of additional controls on JDNI access in log4j.\n\n\u201cJDBC Appender should use JndiManager when accessing JNDI. JNDI access should be controlled via a system property,\u201d states the issue description seen by BleepingComputer.\nSee Also: Complete Offensive Security and Ethical Hacking Course\n\u201cRelated to CVE-2021-44832 where an attacker with permission to modify the logging configuration file can construct a malicious configuration using a JDBC Appender with a data source referencing a JNDI URI which can execute remote code.\u201d\n\nCheckmarx security researcher Yaniv Nizry\u00a0claimed credit for reporting the vulnerability to Apache:\nStay tuned for a blogpost \ud83d\ude09 pic.twitter.com/D56WpVsuF3\n\n\u2014 Yaniv Nizry (@YNizry) December 28, 2021\nNizry\u2019s tweet quickly exploded in traffic, attracting remarks and memes\u00a0from security experts and \u2018victims\u2019 of the ongoing log4j-patching fatigue.\n\n\u201cI hope this is a joke, I\u00a0hope so much\u2026\u00a0#log4j,\u201d tweeted\u00a0one user in response.\n\n\u201cWe are LONG past the point where the only responsible thing to do is put up a giant flashing neon sign that reads \u2018LOG4J CANNOT BE FIXED, DO NOT USE IT FOR ANYTHING.'\u201d taunted\u00a0another.\n\nSecurity expert Kevin Beaumont labeled\u00a0the instance another \u201cfailed Log4j disclosure in motion\u201d\u00a0during the holidays.\nSee Also: Hackers start pushing malware in worldwide Log4Shell attacks Disclosed too soon?At the time of\u00a0Nizry\u2019s tweet,\u00a0BleepingComputer did not see an official advisory or memo\u00a0indicating the presence of\u00a0an RCE bug in log4j 2.17.\n\nThe tweet itself contained no details about the vulnerability or how it could\u00a0be exploited but, within minutes, led\u00a0a pack of security pros and netizens to start investigating the claim.\n\nDisclosing security vulnerabilities prematurely can lure threat actors to conduct malicious scanning and exploitation activities, as evident from the Log4Shell exploit leak of December 9th.\n\n \nMarc Rogers, VP of cybersecurity at Okta first disclosed the vul[...]\n\n___________________________ \n@hacking_Attack\n@Hacking_Video", "creation_timestamp": "2026-09-01T20:02:01.291068Z"}