graylog2-server Session Fixation vulnerability through cookie injection
Key facts
- Attack vector
- Network
- Privileges required
- High
- User interaction
- Required
- Attack complexity
- High
- Impact type
- Spoofing
- Confidentiality · integrity · availability
- High · High · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA and GitHub. Impact type from CWE-384.
Summary
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| Graylog2 | graylog2-server | 4.3.0 to before 5.1.11; 5.2.0 to before 5.2.4 | 5.1.11, 5.2.4 | Patch available | CNA |
| — | org.graylog2:graylog2-server (Maven) | 4.3.0 to before 5.1.11 | 5.1.11 | Patch available | GHSA-3xf8-g8gr-g7rh |
| — | org.graylog2:graylog2-server (Maven) | 5.2.0-alpha.1 to before 5.2.4 | 5.2.4 | Patch available | GHSA-3xf8-g8gr-g7rh |
- graylog2-server VendorGraylog2 Affected 4.3.0 to before 5.1.11; 5.2.0 to before 5.2.4 Fixed in 5.1.11, 5.2.4 Patch available CNA
- org.graylog2:graylog2-server (Maven) Vendor— Affected 4.3.0 to before 5.1.11 Fixed in 5.1.11 Patch available GHSA-3xf8-g8gr-g7rh
- org.graylog2:graylog2-server (Maven) Vendor— Affected 5.2.0-alpha.1 to before 5.2.4 Fixed in 5.2.4 Patch available GHSA-3xf8-g8gr-g7rh
Remediation
- Fix · CNA graylog2-server (Graylog2) Fixed in 5.1.11, 5.2.4
- Fix · GHSA-3xf8-g8gr-g7rh org.graylog2:graylog2-server (Maven) Fixed in 5.1.11 Advisory →
- Fix · GHSA-3xf8-g8gr-g7rh org.graylog2:graylog2-server (Maven) Fixed in 5.2.4 Advisory →
Timeline
- 2026-10-02 Threatist record created from CVE-2024-24823
- 2026-10-03 Alias added: GHSA-3xf8-g8gr-g7rh
References
Patch 2
Advisory 2
More Graylog2 Graylog vulnerabilities
- TI-2024-16341 graylog2-server vulnerable to instantiation of arbitrary classes triggered by API request CVSS 3.1HIGH 8.8
- TI-2023-21671 Insecure source port usage for DNS queries in Graylog CVSS 3.1MEDIUM 5.3
- TI-2026-01133 Incorrect management of session invalidation vulnerability in Graylog Web Interface CVSS 4.0CRITICAL 9.3
- TI-2023-21667 User session is still usable after logout in graylog2-server CVSS 3.1LOW 3.1
- TI-2021-15624 A Session ID leak in the audit log in Graylog before 4.1.2 allows attackers to escalate… CVSS 3.1CRITICAL 9.8
- TI-2021-15623 A Session ID leak in the DEBUG log file in Graylog before 4.1.2 allows attackers to… CVSS 3.1CRITICAL 9.8
Sources
- CVE-2024-24823 · CVE Program
- CVE-2024-24823 · NVD
- FIRST EPSS
- GHSA-3xf8-g8gr-g7rh · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences