spring-pulsar is vulnerable to Deserialization of Untrusted Data
81
High Risk
JsonPulsarHeaderMapper matched type headers against trusted packages using a prefix check, meaning that trusting any package implicitly trusted all of its subpackages. Additionally, an empty trusted-packages configuration fell back to trusting all packages rather than applying a safe default allow-list. Combined with Jackson's default bean deserialization, a producer could supply crafted header values that caused the consumer to deserialize arbitrary JDK types, including classes whose constructors carry side effects such as allocating file descriptors or spawning thread pools.
You are affected if you are using a version that falls within the vulnerable range.
spring-pulsar is vulnerable to Deserialization of Untrusted Data in versions 0.0.1 - 1.1.17, 1.2.0 - 1.2.17 and 2.0.0 - 2.0.5.
Upgrade the org.springframework.pulsar:spring-pulsar library to the patch version.
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

SOC 2Compliant
ISO 27001Compliant