As reported by upstream: "A new security advisory has been released for Apache Karaf, that is fixed in recent 3.0.9, 4.0.9 and 4.1.1 releases. CVS-2018-11787: Apache Karaf unsecure access to Gogo shell in the webconsole Severity: Moderate Vendor: The Apache Software Foundation Versions Affected: all versions of Apache Karaf prior to 3.0.9, 4.0.9, 4.1.1. Description: 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. This has been fixed in revision: https://gitbox.apache.org/repos/asf?p=karaf.git;h=cfa213a https://gitbox.apache.org/repos/asf?p=karaf.git;h=434e525 https://gitbox.apache.org/repos/asf?p=karaf.git;h=1fc60d7 Mitigation: Apache Karaf users should upgrade to 3.0.9, 4.0.9, 4.1.1 or later as soon as possible. JIRA Tickets: https://issues.apache.org/jira/browse/KARAF-4993 Credit: This issue was reported by Kevin Schmidt" External references: http://karaf.apache.org/security/cve-2018-11787.txt
Impacted: RHOSP 8: org.apache.karaf-karaf-4.0.3.1 RHOSP 9: org.apache.karaf-karaf-3.0.1.1 RHOSP 10: org.apache.karaf-karaf-3.0.3.1 RHOSP 12: org.apache.karaf-karaf-4.0.7.1 Tested on RHOSP8,9,10 & 12 (which ships a vulnerable version of karaf), I was able to gain access to the vulnerable /gogo web console without authentication, simply by installing the webconsole plugin. I did not need to manually install the whiteboard plugin. The regular /system/console/gogo endpoint does require authentication, as expected, however the additional /gogo endpoint does not, and allows full access to the karaf console for the Open Daylight install. These versions should have karaf updated to a supported, fixed, minor version in their relevant major release streams detailed above to fix this vulnerability. Not impacted: RHOSP13: org.apache.karaf-karaf-4.1.5.1 Tested on 8.3.0-4.el7ost, I was not able to get access to the vulnerable /gogo tomcat endpoint by enabling the required features (pax-http-whiteboard/http-whiteboard and webconsole). All access to the web console when accessed via the proper endpoint was authenticated. Which makes sense, because v4.1.5 of karaf is not supposed to be vulnerable per the report.
I have also updated the CVSS on this to reflect the impact to confidentiality and availability, given the web console (if installed) is able to modify certain configuration items, and is able to initiate a shutdown or restart of karaf and likely the host program (via system:shutdown command).
Statement: Open Daylight: The webconsole feature is not installed by default. In RHOSP12 and earlier, when the webconsole feature is installed, the gogo webshell potentially provides access to the Karaf console without authentication.
Generically, I'm also rating this higher across all product which use karaf, given the availability of the shell:exec command and the associated OS-level availability concerns. For example, exec killall java from the webconsole for most karaf applications will cause undesirable availability impact.
This vulnerability is out of security support scope for the following products: * Red Hat JBoss A-MQ 6 * Red Hat JBoss Fuse 6 Please refer to https://access.redhat.com/support/policy/updates/jboss_notes for more details.