Re: Remote code execution exploit found in Log4j ..... -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: Remote code execution exploit found in Log4j .....
From: David Gibbs <david@xxxxxxxxxxxx>
Date: Tue, 14 Dec 2021 11:59:02 -0600
List-archive: <https://archive.midrange.com/midrange-l/>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

On 12/14/21 7:01 AM, Mayer, Michael via MIDRANGE-L wrote:

Good day everyone. This was on Linkedin last night from Scott Forstie ....

https://gist.github.com/forstie/9662d4c302f5224c66b7a4c409141a2c

One thing to keep in mind ... some vendors repackage jar's so their product is included in a single jar, with all the required classes included (either as classes or jar's with a special class loader).

This is going to make it very difficult to detect if the vulnerable classes are used.

david

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Remote code execution exploit found in Log4j ..... , Jack Woehr

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.