Replies posted by UnsuspectingDivinity

2 Replies

U
Do Gooder (Customer)
UnsuspectingDivinityDo Gooder (Customer)
asked in Upgrades & Updates

Filename of log4j is 1.2.17, Microsoft Defender detects 2.x

Hi, I actually saw this really strange thing as well. It seems Oracle has repackaged the log4j-1.2.17.jar to also contain parts of a 2.x log4j. But as the strangely modified log4j-1.2.17.jar file is in the mw_home\mws\oracle_common folder it is safe. It's not used in runtime. This folder is mentioned as safe in the Verification part of the mitigation of Apps10. Scanning tools are very good, but it is difficult to interpret the result - often many "false truths".    /Henrik  Hey Henrik,Thanks for your answer.Safe to say we can just quarantine this file in our IFS and IFS test environments then without any known errors?If so, then it kinda closes the book for us on this (using IFS 9 onprem)Thanks again, Anthony

6
H
Hero (Employee)
2 years ago
U
Do Gooder (Customer)
UnsuspectingDivinityDo Gooder (Customer)
asked in Upgrades & Updates

Filename of log4j is 1.2.17, Microsoft Defender detects 2.x

Thanks, I tried that first; but the bulletin is closed :-( hence my question here.   

6
H
Hero (Employee)
2 years ago

Badges

Show all badges
Terms & ConditionsCookie settings