Skip to content
Fencer Intel
medium 5.3

CVE-2022-22932 json

Path traversal flaws

published 4y ago modified 4mo ago also GHSA-544x-2jx9-4pfg , EUVD-2022-0454

cvss
5.3
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.8%
EPSS 2.8% chance of exploitation in 30 days, percentile 86%
public exploits
0
none known

Summary

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

Patch / fix

  • maven org.apache.karaf:apache-karaf 4.2.15, 4.3.6
  • Apache Software Foundation Apache Karaf 4.2.15, 4.3.6

Is CVE-2022-22932 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2022-22932 updated cvss 5.4

karaf: path traversal flaws

  • Red Hat BPM Suite 6 karaf karaf Red Hat JBoss A-MQ 6 karaf karaf Red Hat JBoss BRMS 6 karaf karaf Red Hat JBoss Data Grid 7 karaf karaf Red Hat JBoss Fuse 6 karaf karaf Red Hat JBoss Fuse Service Works 6 karaf karaf
    affected: no fix planned “Out of support scope”
  • Red Hat Fuse 7.11
    fixed: vendor fix RHSA-2022:5532
  • Red Hat Decision Manager 7 karaf karaf Red Hat Integration Camel K 1 karaf karaf Red Hat Integration Camel Quarkus 1 karaf karaf Red Hat Process Automation 7 karaf karaf
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.75% chance of exploitation in the next 30 days, higher than 86% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:P/I:N/A:N
GitHub 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
maven org.apache.karaf:apache-karaf
>=4.3.0, <4.3.6
<4.2.15
4.3.6
4.2.15

Affected products

  • Apache Software Foundation Apache Karaf

Classification

Weakness
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.