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 |
History
No history.
MITRE Information
Status: PUBLISHED
Assigner: vmware
Published: 2023-08-24T12:59:20.620Z
Updated: 2023-08-24T12:59:20.620Z
Reserved: 2023-05-25T17:21:56.201Z
Link: CVE-2023-34040
JSON object: View
NVD Information
Status : Analyzed
Published: 2023-08-24T13:15:07.453
Modified: 2023-10-18T17:56:38.093
Link: CVE-2023-34040
JSON object: View
Redhat Information
No data.
CWE