Kimai is an open-source time tracking application. Prior to 2.59.0, the KIMAI_SESSION cookie issued after password verification but before TOTP completion is accepted by every /api route because config/packages/security.yaml protects the API with IS_AUTHENTICATED and App\API\Authentication\ApiRequestMatcher routes an existing session through the main firewall. A Scheb TwoFactorToken satisfies that access rule, and App\Voter\ApiVoter grants API access to its User, allowing an attacker with a valid account password to use authenticated REST API operations without entering the second factor even though web routes remain blocked.
This issue is fixed in version 2.59.0.
Attack Parameters
Attack Vector
Network
Can be exploited remotely
Attack Complexity
Low
Easy to exploit
Attack Requirements
None
No additional conditions
Privileges Required
Low
Basic privileges needed
User Interaction
None
No user interaction needed
Impact Assessment
Confidentiality
High
Complete data leak
Integrity
Low
Partial data modification
Availability
None
No disruption
CVSS Vector v4.0
Weakness Type (CWE)
References 5
https://github.com/kimai/kimai/commit/87c85270a98899e6545108cbb9f41103ec6ea312
security-advisories@github.com
https://github.com/kimai/kimai/pull/5957
security-advisories@github.com
https://github.com/kimai/kimai/releases/tag/2.59.0
security-advisories@github.com
https://github.com/kimai/kimai/security/advisories/GHSA-v8hx-4vx8-wc96
security-advisories@github.com
https://www.kimai.org/en/security/ghsa-v8hx-4vx8-wc96
security-advisories@github.com