Graylog concurrent PDF report rendering can leak other users' reports

中 6.5CVE-2024-52506 · GHSA-vggm-3478-vm5m · 18/11/2024 公開 · 17/06/2026 更新

要点

CVE-2024-52506 は org.graylog:graylog-parent, graylog (graylog) に影響する深刻度「中」 (CVSS 6.5) の脆弱性です。
今後30日間に悪用される確率（EPSS）：0.63%（全脆弱性の 50.3% より高い）。
対処：6.1.2 以降に更新してください。

パッケージ	影響を受けるバージョン	修正済みバージョン
org.graylog:graylog-parent Maven	`≥ 6.1.0, < 6.1.2`	`6.1.2`
graylog graylog	`≥ 6.1.0, < 6.1.2`	`6.1.2`

概要

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

NVD の説明

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.