CVE-2018-11787 — apache-karaf
HIGHCVE-2018-11787 is a high-severity (CVSS 8.1) Improper Authentication vulnerability in org.apache.karaf:apache-karaf. A fix is available for org.apache.karaf:apache-karaf — see the affected versions and patch details below.
Improper Authentication in Apache Karaf
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.apache.karaf:apache-karaf☕org.apache.karaf:apache-karaf☕org.apache.karaf:apache-karafReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
In Apache Karaf version prior to 3.0.9, 4.0.9, 4.1.1, when the webconsole feature is installed in Karaf, it is available at .../system/console and requires authentication to access it. One part of the console is a Gogo shell/console that gives access to the command line console of Karaf via a Web browser, and when navigated to it is available at .../system/console/gogo. Trying to go directly to that URL does require authentication. And optional bundle that some applications use is the Pax Web Extender Whiteboard, it is part of the pax-war feature and perhaps others. When it is installed, the Gogo console becomes available at another URL .../gogo/, and that URL is not secured giving access to the Karaf console to unauthenticated users. A mitigation for the issue is to manually stop/uninstall Gogo plugin bundle that is installed with the webconsole feature, although of course this removes the console from the .../system/console application, not only from the unauthenticated endpoint. One could also stop/uninstall the Pax Web Extender Whiteboard, but other components/applications may require it and so their functionality would be reduced/compromised.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.karaf:apache-karaf | all versions | 3.0.9org.apache.karaf:apache-karaf:3.0.9 |
| ☕Maven | org.apache.karaf:apache-karaf | ≥ 4.0.0&&< 4.0.9 | 4.0.9org.apache.karaf:apache-karaf:4.0.9 |
| ☕Maven | org.apache.karaf:apache-karaf | ≥ 4.1.0&&< 4.1.1 | 4.1.1org.apache.karaf:apache-karaf:4.1.1 |
Affected Products
karafapacheDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.karaf:apache-karaf, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.karaf:apache-karaf to 3.0.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-11787 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is CVE-2018-11787 in your dependencies?
Find it across Maven, including transitive dependencies.