Bug 1631100 (CVE-2018-11787)
| Summary: | CVE-2018-11787 karaf: Authentication bypass access to Gogo shell in the webconsole | ||
|---|---|---|---|
| Product: | [Other] Security Response | Reporter: | Pedro Sampaio <psampaio> |
| Component: | vulnerability | Assignee: | Red Hat Product Security <security-response-team> |
| Status: | CLOSED ERRATA | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | unspecified | CC: | aileenc, apevec, chazlett, chrisw, gvarsami, jcoleman, jjoyce, jschluet, ldimaggi, lhh, lpeer, markmc, mburns, mkolesni, nwallace, rbryant, rwagner, sclewis, slinaber, tcunning, tdecacqu, tkirby |
| Target Milestone: | --- | Keywords: | Security |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Karaf 3.0.9, Karaf 4.0.9, Karaf 4.1.1 | Doc Type: | If docs needed, set a value |
| Doc Text: |
Prior to Karaf 3.0.9, Karaf 4.0.9, and Karaf 4.1.1, HTTP endpoints published by Karaf features may also be published under the HTTP web root, in addition to the paths specifically configured by the installed feature. Authentication and access control rules may not cover this additional path, potentially leading to authentication bypass on published features. The Gogo shell provided by the webconsole feature is potentially accessible without authentication as a result.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-10-21 19:53:40 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1654106, 1654107, 1654108, 1654110 | ||
| Bug Blocks: | 1631103 | ||
|
Description
Pedro Sampaio
2018-09-19 21:27:29 UTC
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. |