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.
Remediation
References
https://spring.io/security/cve-2023-34040
Related Vulnerabilities
CVE-2021-40146 Vulnerability in maven package org.apache.any23:apache-any23-core
CVE-2022-22980 Vulnerability in maven package org.springframework.data:spring-data-mongodb
CVE-2014-3630 Vulnerability in maven package com.typesafe.akka:akka-http-xml-experimental_2.11
CVE-2022-46751 Vulnerability in maven package org.apache.ivy:ivy
CVE-2018-1272 Vulnerability in maven package org.springframework:spring-webmvc