Kimai up to 2.12.x API insufficient granularity of access control

Summaryinfo

A vulnerability was found in Kimai up to 2.12.x. It has been classified as problematic. This impacts an unknown function of the component API. This manipulation causes insufficient granularity of access control. This vulnerability is tracked as CVE-2024-29200. The attack is possible to be carried out remotely. No exploit exists. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in Kimai up to 2.12.x. It has been declared as problematic. Affected by this vulnerability is an unknown code block of the component API. The manipulation with an unknown input leads to a insufficient granularity of access control vulnerability. The CWE definition for the vulnerability is CWE-1220. The product implements access controls via a policy or other feature with the intention to disable or restrict accesses (reads and/or writes) to assets in a system from untrusted agents. However, implemented access controls lack required granularity, which renders the control policy too broad because it allows accesses from unauthorized agents to the security-sensitive assets. As an impact it is known to affect confidentiality. The summary by CVE is:

Kimai is a web-based multi-user time-tracking application. The permission `view_other_timesheet` performs differently for the Kimai UI and the API, thus returning unexpected data through the API. When setting the `view_other_timesheet` permission to true, on the frontend, users can only see timesheet entries for teams they are a part of. When requesting all timesheets from the API, however, all timesheet entries are returned, regardless of whether the user shares team permissions or not. This vulnerability is fixed in 2.13.0.

It is possible to read the advisory at github.com. This vulnerability is known as CVE-2024-29200 since 03/18/2024. The exploitation appears to be easy. The attack can be launched remotely. The technical details are unknown and an exploit is not publicly available.

Upgrading to version 2.13.0 eliminates this vulnerability.

Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Name

• Kimai

Version

• 2.0
• 2.1
• 2.2
• 2.3
• 2.4
• 2.5
• 2.6
• 2.7
• 2.8
• 2.9
• 2.10
• 2.11
• 2.12

Website

• Product: https://github.com/kimai/kimai/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion