# CVE-2024-24823: graylog2-server Session Fixation vulnerability through cookie injection

> Attackers can hijack Graylog sessions by injecting cookies during reauthentication, potentially gaining elevated access to user accounts.

- **Severity:** Medium 5.7 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 7 Feb 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-3xf8-g8gr-g7rh

## What is CVE-2024-24823?

CVE-2024-24823 is a medium-severity authentication bypass vulnerability in graylog2-server, published on 7 Feb 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Graylog is a free and open log management platform. Starting in version 4.3.0 and prior to versions 5.1.11 and 5.2.4, 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 a cross-site scripting attack. No such attack has been discovered. 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. Some workarounds are available. 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.

Weakness: CWE-384 (Session Fixation)

## Which versions are affected by CVE-2024-24823?

4 open source packages ship an affected version, including org.graylog2:graylog2-server. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.graylog2:graylog2-server` | Maven | From 4.3.0 | 5.1.11 |
| `org.graylog2:graylog2-server` | Maven | From 4.3.0 | 5.1.11 |
| `org.graylog2:graylog2-server` | Maven | From 5.2.0-alpha.1 | 5.2.4 |
| `org.graylog2:graylog2-server` | Maven | From 5.2.0-alpha.1 | 5.2.4 |

Products: Graylog Graylog.

## How do I fix CVE-2024-24823?

Upgrade org.graylog2:graylog2-server to a fixed version for your release line: 5.1.11 or 5.2.4.

## Is CVE-2024-24823 being exploited?

There is no known exploitation of CVE-2024-24823 in the wild and no public exploit code.

## Other vulnerabilities in graylog2-server

- [CVE-2021-37759](https://insights.sbomify.com/CVE-2021-37759/): Information disclosure in n/a (critical 9.8)
- [CVE-2021-37760](https://insights.sbomify.com/CVE-2021-37760/): Information disclosure in n/a (critical 9.8)
- [CVE-2026-1435](https://insights.sbomify.com/CVE-2026-1435/): Incorrect management of session invalidation vulnerability in Graylog Web Interface (critical 9.3)
- [CVE-2025-53106](https://insights.sbomify.com/CVE-2025-53106/): Graylog vulnerable to privilege escalation through API tokens (high 8.8)
- [CVE-2024-24824](https://insights.sbomify.com/CVE-2024-24824/): graylog2-server vulnerable to instantiation of arbitrary classes triggered by API request (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-24823 and fix it if it is affected.

What it is: CVE-2024-24823 is a medium-severity authentication bypass vulnerability in graylog2-server, published on 7 Feb 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-24823 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.graylog2:graylog2-server (Maven): affected from 4.3.0; fixed in 5.1.11
- org.graylog2:graylog2-server (Maven): affected from 4.3.0; fixed in 5.1.11
- org.graylog2:graylog2-server (Maven): affected from 5.2.0-alpha.1; fixed in 5.2.4
- org.graylog2:graylog2-server (Maven): affected from 5.2.0-alpha.1; fixed in 5.2.4

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-24823/ (Markdown: https://insights.sbomify.com/CVE-2024-24823/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-24823
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-24823
- OSV: https://osv.dev/vulnerability/CVE-2024-24823

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-24823/
Summaries are generated and may contain mistakes; the official description above is the record.