I believe you are reading that wrong. It is log4j2 libarary and 1.11.13 version of the pax code.
Notice the full path "org\ops4j\pax\logging\pax-logging-log4j2\1.11.13"
Original Message:
Sent: 06-23-2022 05:33
From: Rodrigo Esteban
Subject: log4j security compliance -- CVE-2021-44228
Hi,
We are trying the new Pentaho version 9.3 that is announced as getting log4j vulnerability patched. But found these libraries once installed:
- c$\Program Files (x86)\Pentaho Data Integration\lib\log4j-core-2.17.1.jar
- c$\Program Files (x86)\Pentaho Data Integration\lib\log4j-core-2.17.1.jar
- c$\Program Files (x86)\Pentaho Data Integration\system\karaf\system\org\ops4j\pax\logging\pax-logging-log4j2\1.11.13\pax-logging-log4j2-1.11.13.jar
- c$\Program Files (x86)\Pentaho Data Integration\system\karaf\system\org\ops4j\pax\logging\pax-logging-log4j2\1.11.13\pax-logging-log4j2-1.11.13.jar
As you can see, the two first .jar have the version 2.17 wich is log4j vulnerable but the two last still have version 1.11 wich is log4j vulnerable having JMSAppender.class inside.
This cause our vulnerability detection agent to detect the Pentaho version 9.3 as vulnerable.
Is going the provider to launch a new version whith these libraries fixed ?
Thanks in advanced
------------------------------
Rodrigo Esteban
Systems Engineer
Banco Bilbao-Vizcaya Argentaria (BBVA)
Original Message:
Sent: 05-05-2022 15:05
From: Stephen Donovan
Subject: log4j security compliance -- CVE-2021-44228
Pentaho EE releases were patched in the February Service Packs (March 01, 2022 releases 8.3.0.26 and 9.2.0.3). 9.3 is planned to be released this week for EE and CE and will also include those patches.
------------------------------
Stephen Donovan
Digital Solutions Architect
Hitachi Vantara
Original Message:
Sent: 12-29-2021 07:45
From: Rodrigo Esteban
Subject: log4j security compliance -- CVE-2021-44228
Hi,
Please, I'm interested on the same question as WEN
will Pentaho Community edition get updated regarding this log4j vulnerability? when?
We have Pentaho Community Data integration 9.0.0.0 and have found JMSAppender.class in these 2 .jar:
1) C:\Program Files (x86)\Pentaho Data Integration\lib\log4j-1.2.17.jar
2) C:\Program Files (x86)\Pentaho Data Integration\system\karaf\system\org\ops4j\pax\logging\pax-logging-log4j2\1.10.2\pax-logging-log4j2-1.10.2.jar
Can we delete the class in both jar without afecting functionality?
Thanks
------------------------------
Rodrigo Esteban
Systems Engineer
Banco Bilbao-Vizcaya Argentaria (BBVA)
Original Message:
Sent: 12-22-2021 04:04
From: WEN JING
Subject: log4j security compliance -- CVE-2021-44228
will Pentaho Community edition get updated regarding this log4j vulnerability?
Or we can implement the mitigation (remove the JMSAppender class from log4j.jar files) directly and the Pentaho / Spoon still works?
------------------------------
WEN JING
IT Support Manager
NCS Pte Ltd
Original Message:
Sent: 12-16-2021 03:45
From: Martin Rupp
Subject: log4j security compliance -- CVE-2021-44228
Matt - my colleagues have created the scanner.
Log4j 1.x had reached end of life! It is a very old lib with many security issues.
(e.g.: https://www.cvedetails.com/cve/CVE-2019-17571/)
Acc. to the German BSI report log4j 1.x must also be replaced by log4j 2.16 (not simple to do it, because software which uses the lib must be changed, too! Issues also with embedded/bundled versions.)
See: https://www.bsi.bund.de/SharedDocs/Cybersicherheitswarnungen/DE/2021/2021-549032-10F2.pdf?__blob=publicationFile&v=4
------------------------------
Martin Rupp
Service Administrator
Siemens AG
Original Message:
Sent: 12-15-2021 15:16
From: Matt Kynaston
Subject: log4j security compliance -- CVE-2021-44228
Martin - good catch with the stuff under system/karaf/caches. I'd scanned a clean build so it wasn't picking those up. For anyone updating things in-place, you'll definitely want to remove that caches directory or you'll still have vulnerable versions of the library in use. The caches directory will get recreated on next startup.
I can't find any evidence of a bundled log4j (any version) in kettle-log4j-core in my build (9.1.0.8), and the classes there seem to depend on log4j-1.2.17. Out of interest, what tool are you using for scanning? I've been using the one from lunasec: https://github.com/lunasec-io/lunasec/releases/
------------------------------
Matt Kynaston
Chief Technology Officer
Claritum Ltd
Original Message:
Sent: 12-15-2021 11:56
From: Martin Rupp
Subject: log4j security compliance -- CVE-2021-44228
I don't know if spoon uses all of this log4j libraries. But this is not important.
The management don't want that log4j libs < version 2.16 are present.
Log4j 2 is not compatible to log4j 1.
But there is a mode to simulate log4j 1 with some constraints and risks.
https://logging.apache.org/log4j/2.x/manual/compatibility.html
Unfortunately the scan process finds also files which are only bridges to log4j!
E.g.: http://www.slf4j.org/legacy.html
------------------------------
Martin Rupp
Service Administrator
Siemens AG
Original Message:
Sent: 12-15-2021 07:18
From: Daniel Michael Lozynski
Subject: log4j security compliance -- CVE-2021-44228
Does Spoon uses those .jars internally for logging? I created a job, some task where logging is not enabled. Still, when I delete the .jar from the folder/s - Spoon wont start.
I assume it must be used within Spoon then? I also asume it's not possible to simple exchange the .jar with a 2.15.x .jar?
------------------------------
Daniel Michael Lozynski
Product Manager
DB Systel GmbH
Original Message:
Sent: 12-15-2021 05:46
From: Martin Rupp
Subject: log4j security compliance -- CVE-2021-44228
We have now a scanner for log4j in the company.
It has found these locations in PDI 9.2 Community Edition:
D:\Tools\Pentaho Data Integration\pdi-ce-9.2.0.0-290\data-integration\lib\apache-log4j-extras-1.2.17.jar contains Log4J-1.x 1.2.17 __END_OF_LIFE_VERSION__
D:\Tools\Pentaho Data Integration\pdi-ce-9.2.0.0-290\data-integration\lib\apache-log4j-extras-1.2.17.jar contains Log4J-1.x __END_OF_LIFE_VERSION__
D:\Tools\Pentaho Data Integration\pdi-ce-9.2.0.0-290\data-integration\lib\kettle-log4j-core-9.2.0.0-290.jar contains Log4J-2.x 9.2.0.0-290 __VULNERABLE__
D:\Tools\Pentaho Data Integration\pdi-ce-9.2.0.0-290\data-integration\lib\log4j-1.2.17.jar contains Log4J-1.x 1.2.17 __END_OF_LIFE_VERSION__
D:\Tools\Pentaho Data Integration\pdi-ce-9.2.0.0-290\data-integration\lib\log4j-1.2.17.jar contains Log4J-1.x __END_OF_LIFE_VERSION__
D:\Tools\Pentaho Data Integration\pdi-ce-9.2.0.0-290\data-integration\lib\log4jdbc-1.2.jar contains Log4J-1.x 1.2 __END_OF_LIFE_VERSION__
D:\Tools\Pentaho Data Integration\pdi-ce-9.2.0.0-290\data-integration\lib\slf4j-log4j12-1.7.12.jar contains Log4J-1.x 1.7.12 __END_OF_LIFE_VERSION__
D:\Tools\Pentaho Data Integration\pdi-ce-9.2.0.0-290\data-integration\plugins\elasticsearch-bulk-insert-plugin\lib\log4j-api-2.11.1.jar contains Log4J-2.x 2.11.1 __VULNERABLE__
D:\Tools\Pentaho Data Integration\pdi-ce-9.2.0.0-290\data-integration\system\karaf\caches\spoon\data-1\cache\bundle243\version0.0\bundle.jar contains Log4J-2.x 9.2.0.0-290 __VULNERABLE__
D:\Tools\Pentaho Data Integration\pdi-ce-9.2.0.0-290\data-integration\system\karaf\caches\spoon\data-1\cache\bundle6\version0.0\bundle.jar contains Log4J-1.x __END_OF_LIFE_VERSION__
D:\Tools\Pentaho Data Integration\pdi-ce-9.2.0.0-290\data-integration\system\karaf\caches\spoon\data-1\cache\bundle7\version0.0\bundle.jar contains Log4J-2.x 2.8.2 __VULNERABLE__
D:\Tools\Pentaho Data Integration\pdi-ce-9.2.0.0-290\data-integration\system\karaf\caches\spoon\data-1\cache\bundle7\version0.0\bundle.jar contains Log4J-2.x 2.8.2 __VULNERABLE__
D:\Tools\Pentaho Data Integration\pdi-ce-9.2.0.0-290\data-integration\system\karaf\caches\spoon\data-1\cache\bundle7\version0.0\bundle.jar contains Log4J-1.x 1.10.2 __END_OF_LIFE_VERSION__
D:\Tools\Pentaho Data Integration\pdi-ce-9.2.0.0-290\data-integration\system\karaf\caches\spoon\data-1\cache\bundle7\version0.0\bundle.jar contains Log4J-2.x >= 2.0-beta9 (< 2.10.0) __VULNERABLE__
D:\Tools\Pentaho Data Integration\pdi-ce-9.2.0.0-290\data-integration\system\karaf\caches\spoon\data-1\tmp\8ddfb285-kettle-log4j-core-9.2.0.0-290.jar contains Log4J-2.x 9.2.0.0-290 __VULNERABLE__
D:\Tools\Pentaho Data Integration\pdi-ce-9.2.0.0-290\data-integration\system\karaf\system\org\hitachivantara\pax-logging-api-wrap\1.10.2\pax-logging-api-wrap-1.10.2.jar contains Log4J-1.x __END_OF_LIFE_VERSION__
D:\Tools\Pentaho Data Integration\pdi-ce-9.2.0.0-290\data-integration\system\karaf\system\org\ops4j\pax\logging\pax-logging-api\1.10.2\pax-logging-api-1.10.2.jar contains Log4J-1.x __END_OF_LIFE_VERSION__
D:\Tools\Pentaho Data Integration\pdi-ce-9.2.0.0-290\data-integration\system\karaf\system\org\ops4j\pax\logging\pax-logging-log4j2\1.10.2\pax-logging-log4j2-1.10.2.jar contains Log4J-2.x 2.8.2 __VULNERABLE__
D:\Tools\Pentaho Data Integration\pdi-ce-9.2.0.0-290\data-integration\system\karaf\system\org\ops4j\pax\logging\pax-logging-log4j2\1.10.2\pax-logging-log4j2-1.10.2.jar contains Log4J-2.x 2.8.2 __VULNERABLE__
D:\Tools\Pentaho Data Integration\pdi-ce-9.2.0.0-290\data-integration\system\karaf\system\org\ops4j\pax\logging\pax-logging-log4j2\1.10.2\pax-logging-log4j2-1.10.2.jar contains Log4J-1.x 1.10.2 __END_OF_LIFE_VERSION__
D:\Tools\Pentaho Data Integration\pdi-ce-9.2.0.0-290\data-integration\system\karaf\system\org\ops4j\pax\logging\pax-logging-log4j2\1.10.2\pax-logging-log4j2-1.10.2.jar contains Log4J-2.x >= 2.0-beta9 (< 2.10.0) __VULNERABLE__
D:\Tools\Pentaho Data Integration\pdi-ce-9.2.0.0-290\data-integration\system\karaf\system\org\pentaho\di\plugins\kettle-log4j-core\9.2.0.0-290\kettle-log4j-core-9.2.0.0-290.jar contains Log4J-2.x 9.2.0.0-290 __VULNERABLE__
------------------------------
Martin Rupp
Service Administrator
Siemens AG
Original Message:
Sent: 12-14-2021 14:54
From: Dhruvesh Patel
Subject: log4j security compliance -- CVE-2021-44228
so far I found this https://support.pentaho.com/hc/en-us/articles/4416229254541-log4j-2-zero-day-vulnerability-CVE-2021-44228-
on pentaho site regarding log4j-2 vulnerability
------------------------------
Dhruvesh Patel
Data Service Manager
Graham Capital
Original Message:
Sent: 12-13-2021 17:33
From: Matt Kynaston
Subject: log4j security compliance -- CVE-2021-44228
I'm on Pentaho BI server 9.1. This ships log4j 2.8.2 hidden in pentaho-solutions/system/karaf/system/org/ops4j/pax/logging/pax-logging-log4j2/1.10.2/pax-logging-log4j2-1.10.2.jar.
I have no idea where that might be used, but the only mitigation I can find is to remove JndiLookup.class from the jar (naturally you'll want to backup and test before rolling it out):
zip -q -d \
pentaho-solutions/system/karaf/system/org/ops4j/pax/logging/pax-logging-log4j2/1.10.2/pax-logging-log4j2-1.10.2.jar \
org/apache/logging/log4j/core/lookup/JndiLookup.class
------------------------------
Matt Kynaston
Chief Technology Officer
Claritum Ltd
Original Message:
Sent: 12-13-2021 17:17
From: Wesley Massaker
Subject: log4j security compliance -- CVE-2021-44228
We are also using community edition (9.1), but from everything I can tell, the original poster is correct in that Pentaho uses 1.x version, which I don't believe is affected by this weekend's log4j vulnerability. I read up a little on it (not an expert on this btw), and I could not find the classes referenced in that vulnerability. Here's what I was going from when trying to troubleshoot...
https://www.socinvestigation.com/apache-log4j-vulnerability-detection-and-mitigation/
However, 1.x is no longer supported and apparently has it's own vulnerability that was never patched up due to EOL, so I guess the question is how do we move Pentaho up to log4j2 v2.15?
------------------------------
Wesley Massaker
HelpDesk Support
FitzMark Inc
Original Message:
Sent: 12-10-2021 15:54
From: IAN BEATTY
Subject: log4j security compliance -- CVE-2021-44228
There's a questionably large RCE exploit announced today (https://nvd.nist.gov/vuln/detail/CVE-2021-44228) that may or may not impact pdi. The more I read about it, the more obvious it becomes that this is a way larger issue than we (as of this writing) understand.
pdi-ce 9.2 still uses a log4j jar from 2012 that hit EOL in 2015. 1.x versions aren't even tested for security compliance by the log4j team anymore (you know, because EOL...) and they urge anyone using log4j to update to 2 in order to receive security updates.