Privlidge escalation and unauthorised access to logs in Eclipse Kura LogServlet

The Eclipse Foundation is a Common Vulnerabilities and Exposures (CVE) Numbering Authority. This issue it used to request and track the progress of the assignment of a CVE for a vulnerability in the project code for an Eclipse open source project.

Basic information

Project name: Eclipse Kura

Project id: iot.kura

Request type: reservation

Versions affected: 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]

Common Weakness Enumeration:

• {CWE-303: Incorrect Implementation of Authentication Algorithm}

Common Vulnerability Scoring System: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N (7.5 HIGH)

Summary:

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.

Links:

• vulnerability-reports#188 (closed)

Credits: Davide Virruso of Yoroi

Tracking

This section will completed by the project team.

• Reserve an entry only
• We're ready for this issue to be reported to the central authority (i.e., make this public now)

Note that for those projects that host their repositories on GitHub, the use of GitHub Security Advisories is recommended but is not required.

This section will be completed by the EMO.

CVE: {cve}

• All required information is provided
• CVE Assigned
• Pushed to Mitre
• Accepted by Mitre

assigned to @ntimeus, @mbarbero, and @mrybczyn

We will use CVE-2024-3046

Please note that this entry is not published yet and do not use the CVE ID in public materials for now.

made the issue visible to everyone

assigned to @mmaiero

made the issue confidential

@ntimeus @mmaiero I need your help to specify the CWE (Weekness enumeration). What is the reason for the issue? Missing validation?

changed the description

I also propose the following CVSS: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L which decodes to:

Attack Vector (AV) = Network (N)

Attack Complexity (AC) = Low (L)

Privileges Required (PR) = None (N)

User Interaction (UI) = None (N)

Scope (S) = Unchanged (U)

Confidentiality (C) = High (H)

Integrity (I) = Low (L)

Availability (A) = Low (L)

Do you agree with the assesment?

Hi, yes, confirmed.

mentioned in issue vulnerability-reports#188 (closed)

changed the description

changed the description

marked the checklist item All required information is provided as completed

marked the checklist item CVE Assigned as completed

The entry has been published. I'm removing the confidential tag.

closed

made the issue visible to everyone

marked the checklist item We're ready for this issue to be reported to the central authority (i.e., make this public now) as completed