Description (CNA)
Graylog is a free and open log management platform. From 6.2.0 until 6.3.12, 7.0.7, and 7.1.2, the DELETE /users/{userId}/tokens/{idOrToken} endpoint implemented by UsersResource.revokeToken() in graylog2-server/src/main/java/org/graylog2/rest/resources/users/UsersResource.java checks USERS_TOKENREMOVE permission against the attacker-controlled userId path parameter before resolving the token selected by idOrToken. An authenticated user can provide an authorized userId while accessTokenService.loadById() or accessTokenService.load() resolves a token belonging to another user, including a service account or administrator, after which accessTokenService.destroy() deletes that token without checking AccessToken.getUserName(). The issue does not expose token contents, but unauthorized deletion causes integrity impact and can disrupt access-token-based integrations. This issue is fixed in versions 6.3.12, 7.0.7, and 7.1.2.
Affected (CNA)
| Vendor / product | Versions |
|---|---|
| Graylog2 / graylog2-server | affected >= 6.2.0, < 6.3.12; affected >= 7.0.0-alpha.1, < 7.0.7; affected >= 7.1.0-alpha.1, < 7.1.2 |
CWE
CWE-639
References
- https://github.com/Graylog2/graylog2-server/security/advisories/GHSA-j769-9gv9-65gr
- https://github.com/Graylog2/graylog2-server/pull/26049
- https://github.com/Graylog2/graylog2-server/pull/26051
- https://github.com/Graylog2/graylog2-server/pull/26053
- https://github.com/Graylog2/graylog2-server/pull/26055
- https://github.com/Graylog2/graylog2-server/commit/41d3745d0e52736d06c07d279ca0d72c1616df4c
- https://github.com/Graylog2/graylog2-server/commit/4f280138b53dc3bbb5749213e8cb1c8e372f23a2
- https://github.com/Graylog2/graylog2-server/commit/84b0ffa0bdf918f6edd2bb23a47254088634b1fc
- https://github.com/Graylog2/graylog2-server/commit/e5accc5f4ce48bd61b84bb8e5a13d21f8eac3da5
ADP enrichment
No English description supplied.
No references supplied.