Get ahead
VMware offers training and certification to turbo-charge your progress.
Learn moreJsonKafkaHeaderMapper and the deprecated DefaultKafkaHeaderMapper check the header type requested in the spring_json_header_types header against the mapper's trusted packages before deserializing a header value. Because java.lang is trusted by default, the type java.lang.Class passes this check. Deserializing a java.lang.Class header resolves the header value as a class name and loads that class, but the class named in the value is not subject to the trusted packages check.
A malicious producer can use this to make the consumer load, and with some Jackson versions initialize, any class on the consumer's classpath, regardless of the trusted packages configuration. The impact depends on the side effects of the static initializers of the classes present on the classpath, such as resource allocation, driver registration, or blocking.
An application is affected if it consumes records from a topic that an attacker can produce to and maps inbound headers with JsonKafkaHeaderMapper or DefaultKafkaHeaderMapper, which is the default when Jackson is on the classpath.
Spring for Apache Kafka:
| Fix version | Availability |
|---|---|
| 4.1.3 | OSS |
| 4.1.2.1 | Enterprise Support Only |
| 4.0.9 | OSS |
| 4.0.8.1 | Enterprise Support Only |
| 3.3.18 | Enterprise Support Only |
| 2.9.16 | Enterprise Support Only |
| 2.8.14 | Enterprise Support Only |
Users of affected versions should upgrade to the corresponding fixed version.
In the fixed versions, java.lang.Class is never trusted, even when java.lang or * is trusted, and headers of this type (and arrays of it) are returned to the application as a NonTrustedHeaderType. Applications that need to convey a class in a header should send the class name as a String (for example, OrderEvent.class.getName()) and resolve it in the consuming application against the classes they expect.
To report a security vulnerability for a project within the Spring portfolio, see the Security Policy