Description
In Apache Karaf prior to 4.2.0 release, if the sshd service in Karaf is left on so an administrator can manage the running instance, any user with rights to the Karaf console can pivot and read/write any file on the file system to which the Karaf process user has access. This can be locked down a bit by using chroot to change the root directory to protect files outside of the Karaf install directory; it can be further locked down by defining a security manager policy that limits file system access to those directories beneath the Karaf home that are necessary for the system to run. However, this still allows anyone with ssh access to the Karaf process to read and write a large number of files as the Karaf process user.
Remediation
References
http://karaf.apache.org/security/cve-2018-11786.txt
https://issues.apache.org/jira/browse/KARAF-5427
https://lists.apache.org/thread.html/5b7ac762c6bbe77ac5d9389f093fc6dbf196c36d788e3d7629e6c1d9%40%3Cdev.karaf.apache.org%3E
Related Vulnerabilities
CVE-2023-34062 Vulnerability in maven package io.projectreactor.netty:reactor-netty-http
CVE-2017-5651 Vulnerability in maven package org.apache.tomcat.embed:tomcat-embed-core
CVE-2022-31069 Vulnerability in npm package @ffdc/nestjs-proxy
CVE-2020-17530 Vulnerability in maven package org.apache.struts:struts2-core
CVE-2021-32731 Vulnerability in maven package org.xwiki.platform:xwiki-platform-web