CVE-2024-3046: Eclipse Kura LogServlet Vulnerability

Summary

09/04/2024
No i
High
7.5

CVE-2024-3046: Eclipse Kura LogServlet vulnerability. Affects org.eclipse.kura:org.eclipse.kura.web2 versions >= 2.0.600, <= 2.4.0. No fix is published. 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

Eclipse Kura is an open-source framework for building IoT gateways. It provides a platform for developing and managing IoT applications. The LogServlet component in Eclipse Kura versions 5.0.0 to 5.4.1 is vulnerable to an attack where an unauthenticated user can retrieve device logs. Additionally, an attacker can exploit downloaded logs to perform privilege escalation using the session ID of an authenticated user found in the logs.

Vulnerability Detail

The vulnerability in the Eclipse Kura LogServlet component allows unauthorized access to device logs and potential privilege escalation. By sending a specially crafted request to the servlet, an unauthenticated user can retrieve device logs. These logs may contain sensitive information, including session IDs of authenticated users. An attacker can then use this information to escalate their privileges within the system.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, it is advised to restrict access to the LogServlet component or disable it if not required. This can be done by modifying the configuration of the Eclipse Kura gateway. Here is an example of how to disable the LogServlet in the Kura properties file:

org.eclipse.kura.web2.LogServlet.enabled=false

Please note that this workaround may limit the functionality of the gateway and should only be used until a proper fix can be applied.

Conclusion

The Eclipse Kura LogServlet vulnerability allows unauthorized access to device logs and potential privilege escalation. It is crucial to upgrade to a fixed version of Eclipse Kura to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for org.eclipse.kura:org.eclipse.kura.web2 →

Share this vulnerability

FAQ

Eclipse Kura is an open-source framework for building IoT gateways. It provides a platform for developing and managing IoT applications.

The vulnerability affects Eclipse Kura versions 5.0.0 to 5.4.1.

By sending a specially crafted request to the LogServlet component, an unauthenticated user can retrieve device logs. These logs may contain sensitive information, such as session IDs, which can be used for privilege escalation.

Yes, upgrading to a version of Eclipse Kura beyond 2.4.0 will include a fix for this vulnerability.

A temporary workaround is to restrict access to the LogServlet component or disable it if not required. However, this may limit the functionality of the gateway and should only be used until a proper fix can be applied.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. 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