Those using JXPath to interpret untrusted XPath expressions may be vulnerable to a remote code execution attack. All JXPathContext class functions processing a XPath string are vulnerable except compile() and compilePath() function. The XPath expression can be used by an attacker to load any Java class from the classpath resulting in code execution. https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=47133
Created apache-commons-jxpath tracking bugs for this issue: Affects: fedora-all [bug 2136132] Created javapackages-bootstrap tracking bugs for this issue: Affects: fedora-all [bug 2136133]
There is an ongoing discussion in the upstream project https://github.com/apache/commons-jxpath/pull/25. It boils don to whether a change in behaviour is acceptable and whether to implements whitelists / blacklists and whether to enable them by default. I don't know what position to take, I would like ask the security team for opinion.
FYI, no package in Fedora requires apache-commons-jxpath.
Correction: maven BuildRequires this package.
This issue has been addressed in the following products: RHINT Camel-Springboot 3.20.1 Via RHSA-2023:2100 https://access.redhat.com/errata/RHSA-2023:2100
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s): https://access.redhat.com/security/cve/cve-2022-41852