Graylog2 Server up to 5.1.10/5.2.3 HTTP PUT Request cluster_config authorization

Summaryinfo

A vulnerability, which was classified as critical, has been found in Graylog2 Server up to 5.1.10/5.2.3. This vulnerability affects unknown code of the file /api/system/cluster_config/ of the component HTTP PUT Request Handler. This manipulation causes authorization. This vulnerability is registered as CVE-2024-24824. Remote exploitation of the attack is possible. No exploit is available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability classified as critical was found in Graylog2 Server up to 5.1.10/5.2.3. Affected by this vulnerability is an unknown functionality of the file /api/system/cluster_config/ of the component HTTP PUT Request Handler. The manipulation with an unknown input leads to a authorization vulnerability. The CWE definition for the vulnerability is CWE-863. The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. This allows attackers to bypass intended access restrictions. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

Graylog is a free and open log management platform. Starting in version 2.0.0 and prior to versions 5.1.11 and 5.2.4, arbitrary classes can be loaded and instantiated using a HTTP PUT request to the `/api/system/cluster_config/` endpoint. Graylog's cluster config system uses fully qualified class names as config keys. To validate the existence of the requested class before using them, Graylog loads the class using the class loader. If a user with the appropriate permissions performs the request, arbitrary classes with 1-arg String constructors can be instantiated. This will execute arbitrary code that is run during class instantiation. In the specific use case of `java.io.File`, the behavior of the internal web-server stack will lead to information exposure by including the entire file content in the response to the REST request. Versions 5.1.11 and 5.2.4 contain a fix for this issue.

The weakness was published 02/07/2024 as GHSA-p6gg-5hf4-4rgj. It is possible to read the advisory at github.com. This vulnerability is known as CVE-2024-24824 since 01/31/2024. Technical details of the vulnerability are known, but there is no available exploit.

Upgrading to version 5.1.11, 5.2.4 or 6.0 eliminates this vulnerability. Applying the patch 75ef2b8d60e7d67f859b79fe712c8ae7b2e861d8 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Vendor

• Graylog2

Name

• Server

Version

• 5.1.0
• 5.1.1
• 5.1.2
• 5.1.3
• 5.1.4
• 5.1.5
• 5.1.6
• 5.1.7
• 5.1.8
• 5.1.9
• 5.1.10
• 5.2.0
• 5.2.1
• 5.2.2
• 5.2.3

License

• open-source

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion