CVE-2024-52506 – org.graylog:graylog-parent

Package

Manager: maven
Name: org.graylog:graylog-parent
Vulnerable Version: >=6.1.0 <6.1.2

Severity

Level: High

CVSS v3.1: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N/E:U/RL:O/RC:C

CVSS v4.0: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

EPSS: 0.00169 pctl0.3855

Details

Graylog concurrent PDF report rendering can leak other users' reports ### 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

Metadata

Created: 2024-11-18T20:02:26Z
Modified: 2024-11-19T20:49:21Z
Source: https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2024/11/GHSA-vggm-3478-vm5m/GHSA-vggm-3478-vm5m.json
CWE IDs: ["CWE-200"]
Alternative ID: GHSA-vggm-3478-vm5m
Finding: F310
Auto approve: 1