Hi Michelle,

in LRE V24.1 is in LoadRunner Enterprise\bin\lib already log4j-2.17.1 installed. No need to fix this

Hi Pascal,

Sorry for the late reply. Our machines have been upgraded to LRE V 24.1. However, when I checked on our LG machines, log4j files are still v.2.17.0. 

I'm at LRE 2023.1.3 and I see log4j-core-2.17.1.jar files. You might check any patches on 2024.1

Thanks for the reply. Do you know where I can find the 2024.1 patches? The one I found was published back in 2022.
portal.microfocus.com/.../KM000003611

Hi Michelle,

I only use LR Host installations. Maybe OT forgot to update the One LG-Package?

There are no more specific Log4J-Updates besides the one you posted, because log4j was directly updated in any other following Version.

log4j-api-2.17.1.jar & log4j-core-2.17.1.jar are installed with Release-Date 27.12.2021.

Did you delete the old folder for a clean new installation before updating

You can do that via support portal, but it might be limited to the 'admin' users of the entitlement. At least I cannot do that for I'm not an admin in my organization in respect to LRE contract.

But I guess you can unpack the patch of 2022 and just copy the the log4j jars around after making a copy. I remember that I did that as well before an official log4j fix was delivered for LRE/LRP..

[EDIT]

I've for testing a VuGen CE 24.1 build 264. In this installation I've log4j 2.17.1 installed. I would not expect inconsistencies between components of the same version.

Thanks for the reply.
I don't remember the log4j version before the upgrade, we didn't do a clean install. After I upgraded our machines from v2021 to v2024.1, our log4j version was 2.13.3. So I looked up patches that are available online. The one that I found only got us to 2.17.0. (And I've applied the fix to ALL the machines, server, controller, and all the LGs). After I applied the fixes, I still need to manually remove the older log4j 2.13.3 files. 

Thanks for the suggestion. I'll see if I can reach out to the admin and get a patch that upgrade log4j to 2.17.1.