Ce mail provient de l'extérieur, restons vigilants

=====================================================================

                            CERT-Renater

                Note d'Information No. 2025/VULN415
_____________________________________________________________________

DATE                : 03/07/2025

HARDWARE PLATFORM(S): /

OPERATING SYSTEM(S): Systems running Graylog versions
                          prior to 6.2.4, 6.3.0-rc.2.

=====================================================================
https://github.com/Graylog2/graylog2-server/security/advisories/GHSA-3m86-c9x3-vwm9
_____________________________________________________________________


Privilege escalation through API tokens
High
boosty published GHSA-3m86-c9x3-vwm9 Jun 30, 2025

Package
No package listed

Affected versions
>=6.2.0

Patched versions
6.2.4, 6.3.0-rc.2


Description
Impact

Graylog users can gain elevated privileges by creating and using API
tokens for the local Administrator or any other user for whom the
malicious user knows the ID.

For the attack to succeed, the attacker needs a user account in
Graylog. They can then proceed to issue hand-crafted requests to
the Graylog REST API and exploit a weak permission check for token
creation.


Workarounds

In Graylog version 6.2.0 and above, regular users can be restricted
from creating API tokens. The respective configuration can be found
in System > Configuration > Users > "Allow users to create personal
access tokens". This option should be Disabled, so that only
administrators are allowed to create tokens.


Recommended Actions

After upgrading Graylog from a vulnerable version to a patched version,
administrators are advised to perform the following steps to ensure
the integrity of their system:

Review API tokens

An overview of all existing API tokens is available at
System > Users and Teams > Token Management. Please review this
list carefully and ensure each token is there for a reason.


Check Audit Log (Graylog Enterprise only)

Graylog Enterprise provides an audit log that can be used to review
which API tokens were created when the system was vulnerable.
Please search the Audit Log for action:create token and match the
Actor with the user for whom the token was created. In most cases
this should be the same user, but there might be legitimate reasons
for users to be allowed to create tokens for other users. If in
doubt, please review the user's actual permissions.


Review API token creation requests

Graylog Open does not provide audit logging, but many setups contain
infrastructure components, like reverse proxies, in front of the
Graylog REST API. These components often provide HTTP access logs.
Please check the access logs to detect malicious token creations by
reviewing all API token requests to the
/api/users/{user_id}/tokens/{token_name} endpoint ({user_id} and
{token_name} may be arbitrary strings).


Severity
High
8.8/ 10

CVSS v4 base metrics
Exploitability Metrics
Attack Vector Network
Attack Complexity Low
Attack Requirements Present
Privileges Required Low
User interaction Active
Vulnerable System Impact Metrics
Confidentiality High
Integrity High
Availability High
Subsequent System Impact Metrics
Confidentiality High
Integrity High
Availability High
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

CVE ID
CVE-2025-53106

Weaknesses
No CWEs


Credits

    @thll thll Finder



=========================================================
+ CERT-RENATER        |    tel : 01-53-94-20-44         +
+ 23/25 Rue Daviel    |    fax : 01-53-94-20-41         +
+ 75013 Paris         |   email:cert@support.renater.fr +
=========================================================