org.apache.karaf:apache-karaf
Maven package
Overview
Package versions
| Versions | Range | Direct vulnerabilities |
|---|---|---|
| 4.4.2 | and later versions | 0C0H0M0L |
| 4.4.0 | up to 4.4.2 | 1C0H0M0L |
| 4.3.8 | up to 4.4.0 | 0C0H0M0L |
| 4.3.6 | up to 4.3.8 | 1C0H0M0L |
| 4.3.0 | up to 4.3.6 | 1C0H1M0L |
| 4.2.15 | up to 4.3.0 | 1C0H0M0L |
| 4.2.3 | up to 4.2.15 | 1C0H1M0L |
| 4.2.0 | up to 4.2.3 | 1C0H2M0L |
| 4.1.1 | up to 4.2.0 | 1C1H2M0L |
| 4.1.0 | up to 4.1.1 | 1C2H2M0L |
| 4.0.10 | up to 4.1.0 | 1C1H2M0L |
| 4.0.9 | up to 4.0.10 | 1C1H3M0L |
| 4.0.8 | up to 4.0.9 | 1C2H3M0L |
| 4.0.0 | up to 4.0.8 | 1C2H4M0L |
| 3.0.9 | up to 4.0.0 | 1C1H4M0L |
| before 3.0.9 | all earlier versions | 1C2H4M0L |
No known vulnerabilities in 4.4.2 and later versions
Nothing in our data affects this version.
16 ranges in total. Each row is a range of versions with the same vulnerabilities, newest first. The data names only the versions where something changes (first affected, fixed), so the versions in between are a range.
Vulnerabilities · 7
| CVE | Severity | Published | Vulnerable | Fixed in |
|---|---|---|---|---|
| CVE-2022-40145karaf: JDBC JAAS LDAP injection | CRITICAL | 21 Dec 2022 | <4.3.8>=4.4.0, <4.4.2 | 4.3.84.4.2 |
| CVE-2022-22932karaf: path traversal flaws | MEDIUM | 26 Jan 2022 | >=4.3.0, <4.3.6<4.2.15 | 4.3.64.2.15 |
| CVE-2019-0191karaf: Zip-slip vulnerability via kar file | MEDIUM | 21 Mar 2019 | <4.2.3 | 4.2.3 |
| CVE-2018-11787karaf: Authentication bypass access to Gogo shell in the webconsole | HIGH | 18 Sep 2018 | <3.0.9>=4.0.0, <4.0.9>=4.1.0, <4.1.1 | 3.0.94.0.94.1.1 |
| CVE-2018-11786karaf: SSH RBAC security enforcement | HIGH | 18 Sep 2018 | <4.2.0 | 4.2.0 |
| CVE-2016-8750karaf: LDAP injection in LDAPLoginModule | MEDIUM | 19 Feb 2018 | <4.0.8 | 4.0.8 |
| CVE-2014-0219Karaf: denial of service via shutdown port | MEDIUM | 15 Nov 2017 | <4.0.10 | 4.0.10 |
OX Radar and Response Center
Find threats in your stack.
OX Radar can check high-priority threats, like critical package CVEs, against your context.
Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.