{"answers":{"affected":"2 open source packages ship an affected version, including kimai/kimai. It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-29200 in the wild and no public exploit code.","fix":"Upgrade kimai/kimai to 2.13.0 or later.","what":"CVE-2024-29200 is a medium-severity missing authorization vulnerability in kimai, published on 28 Mar 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-29200 and fix it if it is affected.\n\nWhat it is: CVE-2024-29200 is a medium-severity missing authorization vulnerability in kimai, published on 28 Mar 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2024-29200 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- kimai/kimai (Packagist): affected all versions; fixed in 2.13.0\n- kimai/kimai (Packagist): affected all versions; fixed in 2.13.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-29200/ (Markdown: https://insights.sbomify.com/CVE-2024-29200/index.md)","id":"CVE-2024-29200","markdown":"https://insights.sbomify.com/CVE-2024-29200/index.md","name":"CVE-2024-29200","record":{"aliases":["GHSA-cj3c-5xpm-cx94"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Kimai time-tracking","requires_auth":"low_privilege","summary":"Attackers can view unauthorized timesheet entries via the API due to inconsistent permission enforcement compared to the UI.","user_interaction":"required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"kimai","vendor":"kimai"}],"cvss":{"score":6.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-1220","name":"Insufficient Granularity of Access Control"}],"description":"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.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"API returns timesheet entries a user should not be authorized to view","id":"CVE-2024-29200","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"missing_authorization","year":"2024"},"n_packages":2,"n_references":1,"next":{"headline":"JumpServer's insecure Ansible playbook validation leads to RCE in Celery","id":"CVE-2024-29201"},"packages":[{"ecosystem":"Packagist","fixed":["2.13.0"],"introduced":["0"],"last_affected":[],"package":"kimai/kimai","purl":null,"source":"GHSA-cj3c-5xpm-cx94"},{"ecosystem":"Packagist","fixed":["2.13.0"],"introduced":["0"],"last_affected":[],"package":"kimai/kimai","purl":"pkg:composer/kimai/kimai","source":"GHSA-cj3c-5xpm-cx94"}],"prev":{"headline":"Unauthenticated views may expose information to anonymous users","id":"CVE-2024-29199"},"products":["kimai"],"published":"2024-03-28","related":[{"cvss_score":9.6,"headline":"Cross-site Scripting in kimai/kimai","id":"CVE-2020-19825","kev_date_added":null,"published":"2023-02-15"},{"cvss_score":8.5,"headline":"Kimai 1.30.10 SameSite Cookie Vulnerability Session Hijacking","id":"CVE-2023-53957","kev_date_added":null,"published":"2025-12-19"},{"cvss_score":7.8,"headline":"Improper Neutralization of Formula Elements in a CSV File in Kimai 2","id":"CVE-2021-43515","kev_date_added":null,"published":"2022-04-08"},{"cvss_score":7.2,"headline":"Kimai (Authenticated) SSTI to RCE by Uploading a Malicious Twig File","id":"CVE-2023-46245","kev_date_added":null,"published":"2023-10-31"},{"cvss_score":6.8,"headline":"Kimai Vulnerable to Authenticated Server-Side Template Injection (SSTI)","id":"CVE-2026-23626","kev_date_added":null,"published":"2026-01-18"},{"cvss_score":6.5,"headline":"Kimai: API invoice endpoint missing customer-level access control (IDOR)","id":"CVE-2026-28685","kev_date_added":null,"published":"2026-03-06"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-02","vendors":["kimai"]},"summary":"Attackers can view unauthorized timesheet entries via the API due to inconsistent permission enforcement compared to the UI.","url":"https://insights.sbomify.com/CVE-2024-29200/"}