CVE-2024-248248.8HighCWE-863

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

Graylog2 · graylog2-server

Affected: graylog2-server · Exploitation: likely to be exploited (10% or more)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

34.7%probability of exploitation in the next 30 days

98th percentile

050100

Higher than 98% of scored CVEs

8.8HighCVSS 3.1

LowMediumHighCrit.

DescriptionCVE.org

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 products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

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

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Likely to be exploited (10% or more). EPSS gives it a 10% or higher chance of exploitation in the next 30 days.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Incorrect Authorization · Access Control
Vendor: Graylog2
Published: February 2024
Band: Likely to be exploited (10% or more), February 2024

CoverageNo articles yet

No CyberSIXT article names CVE-2024-24824 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.