Kimai: Sensitive Cookie with Improper SameSite Attribute
CVE-2023-53957 is a high-severity sensitive cookie with improper samesite attribute vulnerability in Kimai, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, but only if a user takes part, for example by opening a link or file. Affected Kimai versions: 1.30.10. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.59% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of Kimai you run against the affected versions below, and install the vendor's latest release.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
- Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.
Affected products and versions
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- RequiredA user must take an action such as opening a file or link.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 8.5 | High | CNA (vulncheck.com) |
| CVSS 3.1 | 9.8 | Critical | CNA (vulncheck.com) |
| CVSS 3.1 | 8.8 | High | NVD |
Official description
Kimai 1.30.10 contains a SameSite cookie vulnerability that allows attackers to steal user session cookies through malicious exploitation. Attackers can trick victims into executing a crafted PHP script that captures and writes session cookie information to a file, enabling potential session hijacking.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Sensitive Cookie with Improper SameSite Attribute
The SameSite attribute for sensitive cookies is not set, or an insecure value is used.
How developers prevent this class of flaw
- Set the SameSite attribute of a sensitive cookie to Lax or Strict. This instructs the browser to apply this cookie only to same-domain requests, which provides a good Defense in Depth against CSRF attacks. When the Lax value is in use, cookies are also sent for top-level cross-domain navigation via HTTP GET, HEAD, OPTIONS, and TRACE methods, but not for other HTTP methods that are more likely to cause side-effects of state mutation.
More Sensitive Cookie with Improper SameSite Attribute vulnerabilities (CWE-1275)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: yes, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
- github.com/kimai/kimai/releases/tag/1.30.10Product, Release Notes
Third-party and government advisories
- vulncheck.com/advisories/kimai-samesite-cookie-vulnerability-session-hijackingThird Party Advisory
Technical write-ups (may include proof of concept)
- exploit-db.com/exploits/51278Exploit, Third Party Advisory, VDB Entry
Other vulnerabilities in Kimai
- 7.1 High severity
- 9.1 Critical severity
- 8.8 High severity
- 7.5 High severity
- 7.5 High severity
- 8.8 High severity
Recent Sensitive Cookie with Improper SameSite Attribute vulnerabilities
- 7.5 High severity
- 9.8 Critical severity
Spotted an error? Tell us.