CVE-2023-34040

Java Deserialization vulnerability in Spring-Kafka When Improperly Configured

HIGH
7.8
CVSS Score
Published: August 24, 2023 at 12:59 PM UTC
Updated: June 17, 2026 at 06:02 AM UTC
2 products affected across 2 vendorsSpring for Apache KafkaSpring For Apache Kafka

Using Spring For Apache Kafka by Spring?

Get instant alerts when new vulnerabilities affect Spring For Apache Kafka - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 2%
SSVC
No known exploit

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

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.8.1 ≤ v ≤ 2.9.103.0.0 ≤ v ≤ 3.0.9
2.8.x ≤ v < 2.9.112.9.x ≤ v < 2.9.113.0.x ≤ v < 3.0.102.8.x2.9.x3.0.x
Affected range stops below 2.9.11, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.0.10, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

References (1)

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-502

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card