CVE-2024-24823

Workarounds

Using short session expiration and explicit log outs of unused sessions can help limiting the attack vector. Unpatched this vulnerability exists, but is relatively hard to exploit.
A proxy could be leveraged to clear the authentication cookie for the Graylog server URL for the /api/system/sessions endpoint, as that is the only one vulnerable.

Analysis provided by Fabian Yamaguchi - Whirly Labs (Pty) Ltd

Reauthenticating with an existing session cookie would re-use that session id, even if for different user credentials.
In this case, the pre-existing session could be used to gain elevated access to an existing Graylog login session, provided the malicious user could successfully inject their session cookie into someone else's browser.

The complexity of such an attack is high, because it requires presenting a spoofed login screen and injection of a session cookie into an existing browser, potentially through an XSS attack. No such attack has been discovered.

CVE-2024-24823 has a CVSS score of 5.7 (Medium). The vector is network-reachable, high privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (5.1.11, 5.2.4); upgrading removes the vulnerable code path.

Kodem intelligence

Graylog 5.1.11 and 5.2.4, and any versions of the 6.0 development branch contain patches to not re-use sessions under any circumstances, making this type of attack impossible.

1. What is CVE-2024-24823? CVE-2024-24823 is a medium-severity security vulnerability in org.graylog2:graylog2-server (maven), affecting versions >= 4.3.0, < 5.1.11. It is fixed in 5.1.11, 5.2.4.
2. How severe is CVE-2024-24823? CVE-2024-24823 has a CVSS score of 5.7 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of org.graylog2:graylog2-server are affected by CVE-2024-24823? org.graylog2:graylog2-server (maven) versions >= 4.3.0, < 5.1.11 is affected.
4. Is there a fix for CVE-2024-24823? Yes. CVE-2024-24823 is fixed in 5.1.11, 5.2.4. Upgrade to this version or later.
5. Is CVE-2024-24823 exploitable, and should I be worried? Whether CVE-2024-24823 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2024-24823 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2024-24823?
   • Upgrade org.graylog2:graylog2-server to 5.1.11 or later
   • Upgrade org.graylog2:graylog2-server to 5.2.4 or later