Get ahead
VMware offers training and certification to turbo-charge your progress.
Learn moreThe EmbeddedHeadersJsonMessageMapper defaults to an overly permissive header parsing posture in its constructor. When decodeNativeFormat processes raw byte payloads, it deserializes embedded JSON headers into a plain Map and constructs a GenericMessage with MutableMessageHeaders without sanitizing or filtering untrusted header names by default.
As a result, any transport component using EmbeddedHeadersJsonMessageMapper with default settings—such as ZeroMqChannel when receiving raw socket bytes—allows external network peers to supply arbitrary MessageHeaders entries (including sensitive control headers like replyChannel, errorChannel, routingSlip, and json__TypeId__). These injected headers propagate directly into downstream internal components, such as BeanFactoryChannelResolver, through standard handler/error-handler pipelines.
Spring Integration:
| Fix version | Availability |
|---|---|
| 7.1.0.1 | Enterprise Support Only |
| 7.1.1 | OSS |
| 7.0.5.1 | Enterprise Support Only |
| 7.0.6 | OSS |
| 6.5.11 | Enterprise Support Only |
| 6.4.13 | Enterprise Support Only |
| 5.5.22 | Enterprise Support Only |
No further mitigation steps are necessary.
To report a security vulnerability for a project within the Spring portfolio, see the Security Policy