CVE-2023-34040
Spring-Kafka has Java Deserialization vulnerability 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.
How to fix CVE-2023-34040
To remediate CVE-2023-34040, upgrade the affected package to a fixed version below.
- —upgrade to 2.9.11 or later
Is CVE-2023-34040 being exploited?
Moderate — EPSS is 21.4%. Track this CVE but it's not at the top of the prioritisation list.
Affected packages (1)
- >= 2.8.1, < 2.9.11
CVSS scores
| Source | Version | Severity | Vector |
|---|---|---|---|
| osv | CVSS 3.1 | HIGH7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |