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
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2022-22932US | medium5.3 | Exploit | ||
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 n… | ||||
references
External citations — patches, advisories, analysis.
- https://gitbox.apache.org/repos/asf?p=karaf.git;h=36a2bc4WEB
- https://gitbox.apache.org/repos/asf?p=karaf.git;h=52b70cfWEB
- https://github.com/apache/karafPACKAGE
- https://github.com/apache/karaf/pull/1485WEB
- https://issues.apache.org/jira/browse/KARAF-7326WEB
- https://karaf.apache.org/security/cve-2022-22932.txtWEB
- https://nvd.nist.gov/vuln/detail/CVE-2022-22932ADVISORY
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan