← Back
GHSA-j5mc-p8qg-39j7
Vulnerability in kimai/kimai (GHSA-j5mc-p8qg-39j7)
Summary
vulnerability in kimai/kimai (GHSA-j5mc-p8qg-39j7). Risk of unauthorized operations or information disclosure. Exploitable via `GET /en/favorite/timesheet/add/{id}`. Mitigation: upgrade to `2.57.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **GHSA-j5mc-p8qg-39j7** has been found in kimai/kimai.
Attackers can target a specific entry point like `GET /en/favorite/timesheet/add/{id}` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade kimai/kimai to **2.57.0** or later.
If unsure, ask your IT team or search "kimai/kimai GHSA-j5mc-p8qg-39j7" on the vendor's site.
GHSA-j5mc-p8qg-39j7 (kimai/kimai) — CWE-639 /
Attack surface: GET /en/favorite/timesheet/add/{id} / GET /en/favorite/timesheet/remove/{id} / `timesheet.id` / `start_own_timesheet`
Patched: `2.57.0` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-639) exists in kimai/kimai. Attackers reach the vulnerable code path via `GET /en/favorite/timesheet/add/{id}` without authentication.
📍 Affected scope
kimai/kimai — . Attack surface: GET /en/favorite/timesheet/add/{id} / GET /en/favorite/timesheet/remove/{id} / `timesheet.id` / `start_own_timesheet`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **2.57.0**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual `GET /en/favorite/timesheet/add/{id}` requests with malformed payloads or SQL meta-characters. Run `grep -r 'kimai/kimai' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'kimai/kimai' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `kimai/kimai` を grep し、稼働しているサービス・バージョンを把握する。
-
3Hunt for indicators of compromise detect
grep 'GET /en/favorite/timesheet/add/{id}' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `GET /en/favorite/timesheet/add/{id}` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
6Apply patch patch
Upgrade kimai/kimai to 2.57.0ステージング環境で 2.57.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Replay attack against GET /en/favorite/timesheet/add/{id} on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
composer
kimai/kimai
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.57.0"}]}]