log4j2 hitting IBM WAS

Midnight hour update about WAS on IBM i
https://www.ibm.com/support/pages/node/6525706


For more information:

https://www.lunasec.io/docs/blog/log4j-zero-day/
*Updated @ December 10th, 10am PST*

A few hours ago, a 0-day exploit in the popular Java logging library log4j2 was
discovered that results in Remote Code Execution (RCE) by logging a certain
string.

Given how ubiquitous this library is, the impact of the exploit (full
server control), and how easy it is to exploit, the impact of this
vulnerability is quite severe. We're calling it "Log4Shell" for short
(CVE-2021-44228 just isn't as memorable).

The 0-day was tweeted
<https://twitter.com/P0rZ9/status/1468949890571337731> along
with a POC posted on GitHub
<https://github.com/tangxiaofeng7/apache-log4j-poc>. Since this
vulnerability is still very new, there isn't a CVE to track it yet. This
has been published as CVE-2021-44228
<https://www.randori.com/blog/cve-2021-44228/> now.


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to:  7310 Innovation Blvd, Suite 104
          Ft. Wayne, IN 46818
Ship to:  7310 Innovation Blvd, Dock 9C
          Ft. Wayne, IN 46818
http://www.dekko.com

-- 
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing list
To post a message email: [email protected]
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/web400
or email: [email protected]
Before posting, please take a moment to review the archives
at https://archive.midrange.com/web400.