CVE-2022-22932

Path traversal in Apache Karaf

Apache Karaf obr:* commands and run goal on the karaf-maven-plugin have partial path traversal which allows to break out of expected folder. The risk is low as obr:* commands are not very used and the entry is set by user. This has been fixed in revision: https://gitbox.apache.org/repos/asf?p=karaf.git;h=36a2bc4 https://gitbox.apache.org/repos/asf?p=karaf.git;h=52b70cf Mitigation: Apache Karaf users should upgrade to 4.2.15 or 4.3.6 or later as soon as possible, or use correct path. JIRA Tickets: https://issues.apache.org/jira/browse/KARAF-7326

Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.

CVE-2022-22932 has a CVSS score of 5.3 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.3.6, 4.2.15); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

1. What is CVE-2022-22932? CVE-2022-22932 is a medium-severity path traversal vulnerability in org.apache.karaf:apache-karaf (maven), affecting versions >= 4.3.0, < 4.3.6. It is fixed in 4.3.6, 4.2.15. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
2. How severe is CVE-2022-22932? CVE-2022-22932 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of org.apache.karaf:apache-karaf are affected by CVE-2022-22932? org.apache.karaf:apache-karaf (maven) versions >= 4.3.0, < 4.3.6 is affected.
4. Is there a fix for CVE-2022-22932? Yes. CVE-2022-22932 is fixed in 4.3.6, 4.2.15. Upgrade to this version or later.
5. Is CVE-2022-22932 exploitable, and should I be worried? Whether CVE-2022-22932 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2022-22932 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2022-22932?
   • Upgrade org.apache.karaf:apache-karaf to 4.3.6 or later
   • Upgrade org.apache.karaf:apache-karaf to 4.2.15 or later

Other vulnerabilities in org.apache.karaf:apache-karaf