GHSA-j769-9gv9-65gr Graylog token revocation endpoint allows authenticated users to delete other users’ access tokens

• Maven org.graylog2:graylog2-server: >= 6.2.0, < 6.3.12 → fixed in 6.3.12 • Maven org.graylog2:graylog2-server: >= 7.0.0, < 7.0.7 → fixed in 7.0.7 • Maven org.graylog2:graylog2-server: >= 7.1.0, < 7.1.2 → fixed in 7.1.2

Impact Graylog contains an insecure direct object reference (IDOR) vulnerability in the token revocation endpoint. An authenticated user can delete access tokens belonging to other users, including service account tokens and administrator tokens, if they know or can guess a valid token identifier. The issue does not expose token contents, but it allows unauthorized token deletion, leading to integrity impact and potential availability impact for access token based integrations. Patches The issue has been fixed in the following Graylog versions: `6.3.12`, `7.0.7`, `7.1.2`. Users should upgrade to one of these versions or above to remediate the vulnerability. Graylog Cloud has already been patched. Workarounds There are no feasible workarounds for this issue. Upgrading to a patched version is recommended. Customers using Graylog Enterprise or Security can review the audit log[^1] for suspicious activity. Audit log lines for successful token deletions begin with `access token deleted from user`. Credits Thanks to michaelddickenson and sreelim for reporting. [^1]: https://go2docs.graylog.org/current/interacting_with_your_log_data/audit_log.html