Vulnerability · Published Feb 7, 2024 · Assigned by GitHub_M

CVE-2024-24824graylog2-server vulnerable to instantiation of arbitrary classes triggered by API request

High 8.8

In plain English

A high-severity improper access control in graylog2-server from Graylog2. Proof-of-concept exploit code is public. The chance it is exploited in the next 30 days is estimated at 34.7% (higher than 98% of all known vulnerabilities). Ready-made attack tooling exists: public proof-of-concept code. Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)8.8High
Exploit odds (30 days)34.7%top 1.6% of all CVEs
Exploited in the wildNo reportsCISA SSVC: poc
Attack tooling1Public PoC

Official description

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.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Mavenorg.graylog2:graylog2-server5.1.11GHSA-p6gg-5hf4-4rgj
Mavenorg.graylog2:graylog2-server5.2.4GHSA-p6gg-5hf4-4rgj

Affected products (as reported)

VendorProductVersions
Graylog2 graylog2-server >= 2.0.0, < 5.1.11>= 5.2.0, < 5.2.4

Weakness: CWE-284, CWE-863 · Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

References