GCVE - cpe:2.3:a:spring:spring_for_apache_kafka:*:*:*:*:*:*:*:*

Approved changes feed: RSS · Atom

cpe:2.3:a:spring:spring_for_apache_kafka:*:*:*:*:*:*:*:*

part: a version: * update: *

Vendor	Spring (`4c7a31af-cbd7-516f-b1ce-2d5f574797bc`)
Product	Spring For Apache Kafka (`f6851e83-0c2b-5842-a90c-70ed2c1adbc5`)
Edition	*
Language	*
Software edition	*
Target software	*
Target hardware	*
Other	*
Notes	Imported from gcve-enriched-dumps CVE data

PURL mappings

PURL	Source	Last updated
No PURL mappings for this CPE yet.

Vulnerability references

Identifier	cpeApplicability	Submitted	db.gcve.eu details	Rationale
`CVE:CVE-2023-34040`	vulnerable	2026-06-03 14:52:15.463007	Java Deserialization vulnerability in Spring-Kafka When Improperly Configured MEDIUM (5.3) 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. Published: 2023-08-24T12:59:20.620Z Updated: 2024-10-01T16:13:52.394Z Open on db.gcve.eu Reference links https://spring.io/security/cve-2023-34040	Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.