title: Java Deserialization vulnerability in Spring-Kafka When Improperly Configured
description: In Spring for Apache Kafka 3.0.9 and earlier and versions 2.9.10 and earlier, a possible deserialization attack vector existed, but only if unusual configuration was applied. An attacker would have to construct a malicious serialized object in one of the deserialization exception record headers.
Specifically, an application is vulnerable when all of the following are true:
*  The user does not configure an ErrorHandlingDeserializer for the key and/or value of the record
*  The user explicitly sets container properties checkDeserExWhenKeyNull and/or checkDeserExWhenValueNull container properties to true.
*  The user allows untrusted sources to publish to a Kafka topic
By default, these properties are false, and the container only attempts to deserialize the headers if an ErrorHandlingDeserializer is configured. The ErrorHandlingDeserializer prevents the vulnerability by removing any such malicious headers before processing the record.
problem types: CWE-502 Deserialization of Untrusted Data
affected:
{
defaultStatus: unaffected
product: Spring For Apache Kafka
vendor: Spring
versions:
lessThan: 2.9.11, status: affected, version: 2.8.x, versionType: 2.9.11
lessThan: 2.9.11, status: affected, version: 2.9.x, versionType: 2.9.11
lessThan: 3.0.10, status: affected, version: 3.0.x, versionType: 3.0.10
}
metrics:
cvssV3_1: [
attackComplexity: LOW
attackVector: LOCAL
availabilityImpact: LOW
baseScore: 5.3
baseSeverity: MEDIUM
confidentialityImpact: LOW
integrityImpact: LOW
privilegesRequired: LOW
scope: UNCHANGED
userInteraction: NONE
vectorString: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
version: 3.1
]
format: CVSS
scenarios: GENERAL