dbcve.org
KuraApplication · Eclipse

CVE-2024-3046

HIGH · 7.5 CVSS v3.1 Published 2024-04-09
Fix available
A fix is available. Upgrade to after 5.4.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In Eclipse Kura LogServlet component included in versions 5.0.0 to 5.4.1, a specifically crafted request to the servlet can allow an unauthenticated user to retrieve the device logs. Also, downloaded logs may be used by an attacker to perform privilege escalation by using the session id of an authenticated user reported in logs. This issue affects org.eclipse.kura:org.eclipse.kura.web2 version range [2.0.600, 2.4.0], which is included in Eclipse Kura version range [5.0.0, 5.4.1]

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The LogServlet component in Eclipse Kura versions 5.0.0-5.4.1 lacks proper authentication controls, allowing unauthenticated attackers to retrieve device logs via crafted requests. Logs may contain authenticated user session IDs, enabling privilege escalation.

MitigationRestrict access to the LogServlet by implementing authentication/authorization checks, and sanitize log output to remove sensitive session information. Update to Eclipse Kura version 5.4.2 or later which contains the patched org.eclipse.kura.web2 version.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
KuraApplication
Affected:>= 5.0.0, <= 5.4.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed Eclipse Kura version
    Check the Kura version by examining the system information file, typically found in /opt/kura/.kura-version or by querying the Kura package manager. You can also check the version via the Kura web UI under 'System' > 'About' or by running: dpkg -l | grep kura or checking the manifest file in the Kura installation directory.
    Affected if The installed version is between 5.0.0 and 5.4.1 inclusive.
  2. Verify if the LogServlet component is accessible
    Attempt to access the LogServlet endpoint on your Kura instance. Typically this is exposed at /log or /servlet/log paths on the Kura web server port (default 8080 or 8443). Use curl or a browser to send a GET request to these endpoints without providing credentials.
    Affected if The LogServlet responds with log data or accepts requests without requiring authentication.
  3. Check the LogServlet endpoint configuration
    Examine the Kura web server configuration files (usually in /opt/kura/data/httpd.conf or similar) to determine if authentication filters or security constraints are applied to the LogServlet path. Also check the org.eclipse.kura.web.servlet.log.cfg file if it exists in the /opt/kura/cfg/ directory.
    Affected if No authentication or authorization constraints are defined for the LogServlet endpoint, or the configuration allows unauthenticated access.
  4. Inspect recent logs for sensitive session information
    Review the log files in /opt/kura/log/ directory. Search for entries that may contain session IDs, authentication tokens, or user credentials. Use grep to search for patterns like 'session', 'JSESSIONID', 'auth', or 'token' in the log files.
    Affected if Log files contain session IDs, authentication tokens, or other sensitive user session data that could be harvested by an attacker.

You are affected if your Eclipse Kura version falls between 5.0.0 and 5.4.1 and the LogServlet endpoint is accessible without authentication, or if your logs contain exposed session information.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 5.4.1
Interim mitigation

Restrict access to the LogServlet by implementing authentication/authorization checks, and sanitize log output to remove sensitive session information. Update to Eclipse Kura version 5.4.2 or later which contains the patched org.eclipse.kura.web2 version.

Recommended fix Moderate confidence

Eclipse Kura 5.4.2 or later (containing org.eclipse.kura:org.eclipse.kura.web2 version 2.4.1 or later)

  1. 1. Identify the current Eclipse Kura version in use by checking the Kura runtime or deployment configuration
  2. 2. Plan for a maintenance window as upgrading the Kura runtime will require a service restart
  3. 3. Upgrade Eclipse Kura to version 5.4.2 or later, which contains the fix for the LogServlet authentication bypass
  4. 4. Verify the upgrade by confirming the org.eclipse.kura:org.eclipse.kura.web2 dependency is updated to version 2.4.1 or later
  5. 5. After upgrade, verify that unauthenticated requests to the LogServlet endpoint are properly rejected
  6. 6. Review log files to ensure no unauthorized access occurred prior to the upgrade
Caveat Upgrading Kura may require compatibility checks with connected devices, custom bundles, and dependent services; review release notes for any configuration or API changes between 5.0.0-5.4.1 and the target version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Kura Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-3046 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-3046 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data