Is commons-jxpath security vulnerability fixed in BIRT release 4.15 and higher ? #1916
Replies: 2 comments 4 replies
-
It's marked as rejected here: https://nvd.nist.gov/vuln/detail/CVE-2022-41852 To which jar specifically do you refer to by "BIRT Jars". There are a bunch of downloads and many of the zips have various nested jars and wars, so being specific would be helpful. I'd suggest looking at the 4.17 release instead of the 4.15 release because the runtimes were significantly pruned down during the most recent release cycle, especially strange UI dependencies which might resolve the issue for you. In any case, the dependencies of the Designer IDE product on jxpath come from the Platform: eclipse-platform/eclipse.platform.ui#423 So that cannot be fixed by BIRT. But I don't expect that dependency to creep into any of the runtimes that you might be using on servers. It's simply not needed and not used except in the Eclipse IDE itself... Not only that, for what it's worth, the Platform uses of jxpath to look up model elements in the EMF representation of the in-memory UI models so that does not expose anyone or anything to the supposed vulnerabilities involved. |
Beta Was this translation helpful? Give feedback.
-
Hi, |
Beta Was this translation helpful? Give feedback.
-
Hi ,
After upgrading our project to use BIRT 4.15 version, we are facing a critical security issue related to commons-jxpath jar present in BIRT jars. Is the security issue fixed in newer BIRT versions ?
If it is not fixed ,Are there any plans to fix it in future releases ?
The security issue is described in Jxpath Issue.
Is there any alternative for this issue in BIRT 4.15 ?
Beta Was this translation helpful? Give feedback.
All reactions