CVE-2024-24823 json
graylog2-server Session Fixation vulnerability through cookie injection
published 2024-02-07 2 y ago modified 2026-09-10 1 mo ago also GHSA-3xf8-g8gr-g7rh , EUVD-2024-0497
- cvss
- 5.7
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 35%
- public exploits
- 0
- none known
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.
Patch / fix
- maven org.graylog2:graylog2-server 5.1.11, 5.2.4
- graylog graylog 5.1.11, 5.2.4
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
0.41% chance of exploitation in the next 30 days, higher than 35% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.7 | CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:N |
| NVD | 3.1 | 4.4 | CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:L/I:L/A:N |
| GitHub | 3.1 | 5.7 | CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.graylog2:graylog2-server | >=4.3.0, <5.1.11 >=5.2.0-alpha.1, <5.2.4 |
5.1.11 5.2.4 |
Affected products
- Graylog2 graylog2-server
Classification
- Weakness
-
- CWE-384 Session Fixation
References
-
github.com
/Graylog2/graylog2-server/commit/1596b749db86368ba476662f23a0f0c5ec2b5097
web, patch
-
github.com
/Graylog2/graylog2-server/commit/b93a66353f35a94a4e8f3f75ac4f5cdc5a2d4a6a
web, patch
-
github.com
/Graylog2/graylog2-server/security/advisories/GHSA-3xf8-g8gr-g7rh
web, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2024-24823
advisory
-
github.com
/Graylog2/graylog2-server
package
Sources
- CVE List CVE-2024-24823
- GitHub Advisory GHSA-3xf8-g8gr-g7rh
- NVD CVE-2024-24823
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.