CVE-2023-34040

Java Deserialization vulnerability in Spring-Kafka When Improperly Configured

Published Aug 24, 2023 CVSS 3.1 · 5.3 Medium EPSS 2.1% KEV · Not listed
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

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-crqf-q9fp-hwjw Spring-Kafka has Java Deserialization vulnerability When Improperly Configured
References
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
vmware
Published
Updated
Oct 1, 2024, 4:13 PM
Reserved
May 25, 2023, 5:21 PM
Status
Modified
Published
Aug 24, 2023, 1:15 PM
Modified
Jun 17, 2026, 6:02 AM