CVE-2024-52506: Graylog can leak other users' reports via concurrent PDF report rendering
Impact
The reporting functionality in Graylog allows the creation and scheduling of reports which contain dashboard widgets displaying individual log messages or metrics aggregated from fields of multiple log messages. This functionality, as included in Graylog 6.1.0 & 6.1.1, is vulnerable to information leakage triggered by multiple concurrent report rendering requests from authorized users.
When multiple report renderings are requested at the same start time, the headless browser instance used to render the PDF will be reused. Depending on the timing, either a check for the browser instance "freshness" hits, resulting in an error instead of the report being returned, or one of the concurrent report rendering requests "wins" and this report is returned for all report rendering requests that do not return an error. This might lead to one user getting the report of a different user, potentially leaking indexed log messages or aggregated data that this user normally has no access to.
Patches This problem is fixed in Graylog 6.1.2.
Workarounds There is no known workaround besides disabling the reporting functionality.
References
Other sources
Graylog is a free and open log management platform. The reporting functionality in Graylog allows the creation and scheduling of reports which contain dashboard widgets displaying individual log messages or metrics aggregated from fields of multiple log messages. This functionality, as included in Graylog 6.1.0 & 6.1.1, is vulnerable to information leakage triggered by multiple concurrent report rendering requests from authorized users. When multiple report renderings are requested at the same start time, the headless browser instance used to render the PDF will be reused. Depending on the timing, either a check for the browser instance "freshness" hits, resulting in an error instead of the report being returned, or one of the concurrent report rendering requests "wins" and this report is returned for all report rendering requests that do not return an error. This might lead to one user getting the report of a different user, potentially leaking indexed log messages or aggregated data that this user normally has no access to. This problem is fixed in Graylog 6.1.2. There is no known workaround besides disabling the reporting functionality.
— NVD
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2024-52506?
CVE-2024-52506 is classified as a moderate severity vulnerability affecting Graylog versions 6.1.0 and 6.1.1.
How do I fix CVE-2024-52506?
To address CVE-2024-52506, upgrade to Graylog version 6.1.2 or later.
What functionality is impacted by CVE-2024-52506?
CVE-2024-52506 impacts the reporting functionality in Graylog, including the creation and scheduling of reports.
Which versions of Graylog are affected by CVE-2024-52506?
Graylog versions 6.1.0 and 6.1.1 are affected by CVE-2024-52506.
What are the implications of CVE-2024-52506 for users?
Users of Graylog consuming or scheduling reports may be at risk of exposing sensitive log data due to this vulnerability.