Skip to content
Fencer Intel
medium 4.9

CVE-2019-0226 json

Apache Karaf vulnerable to relative path traversal

published 7y ago modified 4mo ago also GHSA-fjw4-39pg-vf4f , EUVD-2022-3800

cvss
4.9
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.8%
EPSS 1.8% chance of exploitation in 30 days, percentile 78%
public exploits
0
none known

Summary

Apache Karaf Config service provides a install method (via service or MBean) that could be used to travel in any directory and overwrite existing file. The vulnerability is low if the Karaf process user has limited permission on the filesystem. Any Apache Karaf version before 4.2.5 is impacted. User should upgrade to Apache Karaf 4.2.5 or later.

Patch / fix

  • maven org.apache.karaf.config:org.apache.karaf.config.core 4.2.5
  • apache karaf 4.2.5

Is CVE-2019-0226 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

Exploit prediction

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

CVSS scores

assigned by version score vector
NVD 3.0 4.9 CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N
NVD 2.0 5.5 AV:N/AC:L/Au:S/C:N/I:P/A:P
GitHub 3.0 4.9 CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N

Affected packages

ecosystem package affected fixed in
maven org.apache.karaf.config:org.apache.karaf.config.core
<4.2.5
4.2.5

Affected products

  • 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.