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.
References
Link | Resource |
---|---|
https://spring.io/security/cve-2023-34040 | Mitigation Vendor Advisory |
https://spring.io/security/cve-2023-34040 | Mitigation Vendor Advisory |
Configurations
Configuration 1 (hide)
|
History
21 Nov 2024, 08:06
Type | Values Removed | Values Added |
---|---|---|
New CVE |
Information
Published : 2023-08-24 13:15
Updated : 2024-11-21 08:06
NVD link : CVE-2023-34040
Mitre link : CVE-2023-34040
CVE.ORG link : CVE-2023-34040
JSON object : View
Products Affected
vmware
- spring_for_apache_kafka
CWE
CWE-502
Deserialization of Untrusted Data