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.
Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-crqf-q9fp-hwjw | Spring-Kafka has Java Deserialization vulnerability When Improperly Configured |
| Link | Providers |
|---|---|
| https://spring.io/security/cve-2023-34040 |
|
Tue, 01 Oct 2024 17:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Status: PUBLISHED
Assigner: vmware
Published:
Updated: 2024-10-01T16:13:52.394Z
Reserved: 2023-05-25T17:21:56.201Z
Link: CVE-2023-34040
Updated: 2024-08-02T15:54:14.211Z
Status : Modified
Published: 2023-08-24T13:15:07.453
Modified: 2024-11-21T08:06:27.340
Link: CVE-2023-34040
No data.
OpenCVE Enrichment
No data.
Github GHSA