Home Cyber Security News Apache Releases Log4j 2.17.1 Fixing Another Code Execution Flaw

Apache Releases Log4j 2.17.1 Fixing Another Code Execution Flaw

by Abeerah Hashim
Code Execution flaw fixed with Apache Log4j 2.17.1

Following the “Log4Shell” mayhem, Apache has released multiple updates to its Log4j library addressing the bugs. Another Log4j update has surfaced online, patching a code execution vulnerability this week. Users must ensure updating to Log4j 2.17.1 to receive the patch.

Log4j 2.17.1 Addresses A Code Execution Bug

Researchers from CheckMarx have shared insights about the vulnerability in the recently released Log4j version 2.17.0.

Apache rolled out this update days after releasing two different updates fixing the critical Log4Shell exploit and related bugs. Specifically, version 2.17.0 arrived as the third major update that fixed a remote code execution vulnerability triggered via WebSocket connections. While it wasn’t as severe a vulnerability as the Log4Shell, it still posed a significant security risk to the users.

While that update seemingly appeared a final release (at least for some time), CheckMarx researchers found another issue affecting this Log4j version.

As elaborated in a post, the researchers found this vulnerability while auditing Log4j “in the hope of finding something interesting.” Eventually, they found a deserialization vulnerability that didn’t use the disabled lookup feature.

Due to the lack of security checks on accessing JDNI access, an adversary could upload malicious Log4j configuration files leading to code execution. The researchers have shared the details and the PoC exploit in their post.

After finding this vulnerability (CVE-2021-44832), the researchers responsibly disclosed it to Apache, which then worked to develop the fix.

Acknowledging the matter in an advisory, Apache described this moderate-severity vulnerability (CVSS 6.6) as,

Apache Log4j2 versions 2.0-beta7 through 2.17.0 (excluding security fix releases 2.3.2 and 2.12.4) are vulnerable to a remote code execution (RCE) attack 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.

Consequently, the vendors fixed it by “limiting JNDI data source names to the java protocol” with the latest Log4j versions. Thus, users should update to Log4j 2.17.1, 2.12.4, and 2.3.2, respectively, to get the patches.

You may also like

Latest Hacking News

Privacy Preference Center


The __cfduid cookie is used to identify individual clients behind a shared IP address and apply security settings on a per-client basis.

cookie_notice_accepted and gdpr[allowed_cookies] are used to identify the choices made from the user regarding cookie consent.

For example, if a visitor is in a coffee shop where there may be several infected machines, but the specific visitor's machine is trusted (for example, because they completed a challenge within your Challenge Passage period), the cookie allows Cloudflare to identify that client and not challenge them again. It does not correspond to any user ID in your web application, and does not store any personally identifiable information.

__cfduid, cookie_notice_accepted, gdpr[allowed_cookies]


DoubleClick by Google refers to the DoubleClick Digital Marketing platform which is a separate division within Google. This is Google’s most advanced advertising tools set, which includes five interconnected platform components.

DoubleClick Campaign Manager: the ad-serving platform, called an Ad Server, that delivers ads to your customers and measures all online advertising, even across screens and channels.

DoubleClick Bid Manager – the programmatic bidding platform for bidding on high-quality ad inventory from more than 47 ad marketplaces including Google Display Network.

DoubleClick Ad Exchange: the world’s largest ad marketplace for purchasing display, video, mobile, Search and even Facebook inventory.

DoubleClick Search: is more powerful than AdWords and used for purchasing search ads across Google, Yahoo, and Bing.

DoubleClick Creative Solutions: for designing, delivering and measuring rich media (video) ads, interactive and expandable ads.



The _ga is asssociated with Google Universal Analytics - which is a significant update to Google's more commonly used analytics service. This cookie is used to distinguish unique users by assigning a randomly generated number as a client identifier. It is included in each page request in a site and used to calculate visitor, session and campaign data for the sites analytics reports. By default it is set to expire after 2 years, although this is customisable by website owners.

The _gat global object is used to create and retrieve tracker objects, from which all other methods are invoked. Therefore the methods in this list should be run only off a tracker object created using the _gat global variable. All other methods should be called using the _gaq global object for asynchronous tracking.

_gid works as a user navigates between web pages, they can use the gtag.js tagging library to record information about the page the user has seen (for example, the page's URL) in Google Analytics. The gtag.js tagging library uses HTTP Cookies to "remember" the user's previous interactions with the web pages.

_ga, _gat, _gid