Graylog is a free and open log management platform. Prior to versions 6.0.14, 6.1.10, and 6.2.0, it is possible to obtain user session cookies by submitting an HTML form as part of an Event Definition Remediation Step field. For this attack to succeed, the attacker needs a user account with permissions to create event definitions, while the user must have permissions to view alerts. Additionally, an active Input must be present on the Graylog server that is capable of receiving form data (e.g. a HTTP input, TCP raw or syslog etc). Versions 6.0.14, 6.1.10, and 6.2.0 fix the issue. No known workarounds are available, as long as the relatively rare prerequisites are met.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:HGraylog
APPGraylog< 6.0.146.1.0 – 6.1.10 (bez)
Related vulnerabilities
Graylog: brak unieważniania sesji po ponownym logowaniu (CWE-613)
A Session ID leak in the DEBUG log file in Graylog before 4.1.2 allows attackers to escalate privileges (to th...
A Session ID leak in the audit log in Graylog before 4.1.2 allows attackers to escalate privileges (to the acc...
Improper Access Control (IDOR) in the Graylog API, version 2.2.3, which occurs when modifying the user ID in t...
Graylog is a free and open log management platform. In versions 6.2.0 to before 6.2.4 and 6.3.0-alpha.1 to bef...