Vulnerability · Published Aug 24, 2023 · Assigned by vmware
CVE-2023-34040Java Deserialization vulnerability in Spring-Kafka When Improperly Configured
Medium 5.3
In plain English
A medium-severity unsafe deserialization in Spring For Apache Kafka from Spring. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 2.1% (higher than 82% of all known vulnerabilities). Ready-made attack tooling exists: public proof-of-concept code. Fixed versions are available - upgrade the affected package.
Official 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.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Maven | org.springframework.kafka:spring-kafka | 2.9.11 | GHSA-crqf-q9fp-hwjw |
| Maven | org.springframework.kafka:spring-kafka | 3.0.10 | GHSA-crqf-q9fp-hwjw |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Spring | Spring For Apache Kafka | 2.8.x – before 2.9.112.9.x – before 2.9.113.0.x – before 3.0.10 |
Weakness: CWE-502 · Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L