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.
| Score | Percentile |
|---|---|
| 0.39% | 60.34% |
| Base score | Version | Severity | Vector |
|---|---|---|---|
| 7.1 | 4.0 | — |
|
| Type | Value |
|---|---|
| GHSA | GHSA-vggm-3478-vm5m ↗ |
| CVE | CVE-2024-52506 ↗ |
| CWE id | Name |
|---|---|
| CWE-200 | Exposure of Sensitive Information to an Unauthorized Actor |
Vulnerable version ranges and first patched releases as published by GitHub.
| Ecosystem | Package | Vulnerable range | First patched | Vulnerable functions |
|---|---|---|---|---|
| maven | org.graylog:graylog-parent | >= 6.1.0, < 6.1.2 | 6.1.2 | — |