CVE-2018-11786: Improper Privilege Management in Apache Karaf

Summary

21/12/2018
Yes i
High
8.8

CVE-2018-11786: Improper Privilege Management in Apache Karaf. Affects org.apache.karaf:apache-karaf versions < 4.2.0. Fixed in 4.2.0. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

Apache Karaf is an open-source OSGi runtime container that provides a lightweight and flexible platform for building and deploying applications. It allows administrators to manage the running instance through an SSH service. The vulnerability in Apache Karaf prior to version 4.2.0 allows users with access to the Karaf console to read and write any file on the file system to which the Karaf process user has access. This can lead to unauthorized access and modification of sensitive files.

Vulnerability Detail

The vulnerability arises from the lack of proper privilege management in Apache Karaf. When the SSH service is enabled, any user with rights to the Karaf console can pivot and gain access to read and write any file on the file system accessible to the Karaf process user. Although measures like chroot and security manager policies can be implemented to restrict file system access, they still allow users with SSH access to the Karaf process to manipulate a significant number of files.

How To Fix

Minimum fixed version

4.2.0

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

If upgrading to the latest version is not immediately feasible, administrators can mitigate the risk by disabling the SSH service in Apache Karaf. By disabling SSH, the vulnerability is effectively neutralized, but it may limit the ability to manage the running instance remotely.

Conclusion

The vulnerability in Apache Karaf prior to version 4.2.0 allows unauthorized users to read and write files on the file system accessible to the Karaf process user. Upgrading to the latest version or disabling the SSH service are the recommended solutions to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for org.apache.karaf:apache-karaf →

Share this vulnerability

FAQ

Apache Karaf is an open-source OSGi runtime container that provides a lightweight and flexible platform for building and deploying applications.

The vulnerability allows users with access to the Karaf console to read and write any file on the file system accessible to the Karaf process user. This can lead to unauthorized access and modification of sensitive files.

To fix this vulnerability, it is recommended to upgrade to Apache Karaf version 4.2.0 or later.

If upgrading to the latest version is not immediately feasible, administrators can mitigate the risk by disabling the SSH service in Apache Karaf.

Implementing chroot and defining a security manager policy that limits file system access can provide additional protection, but upgrading or disabling SSH is the recommended solution.

Related vulnerabilities

Recent vulnerabilities recorded for org.apache.karaf:apache-karaf.

How To Fix

Minimum fixed version

4.2.0

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback