jackson-databind: @JsonView bypass for setterless creator properties
FasterXML jackson-databind
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| com.fasterxml.jackson.core:jackson-databind Maven |
|
|
| tools.jackson.core:jackson-databind Maven |
|
FasterXML jackson-databind
| Product | Affected | Fixed in |
|---|---|---|
| com.fasterxml.jackson.core:jackson-databind Maven |
|
|
| tools.jackson.core:jackson-databind Maven |
|
3.1.4jackson-databind contains the general-purpose data-binding functionality and tree-model for Jackson Data Processor. From 2.21.0 until 2.21.4 and 3.1.4, in BeanDeserializer._deserializeUsingPropertyBased, the active-view (@JsonView) filter was applied only to creator properties; the regular property-buffering branch performed no prop.visibleInView(activeView) check. A change making SetterlessProperty.isMerging() return true routed setterless Collection/Map properties through this unguarded path, so a setterless collection annotated with a restricted @JsonView is populated from attacker JSON even when the active view excludes it. This vulnerability is fixed in 2.21.4 and 3.1.4.
From the CVE record · GitHub_M
In affected jackson-databind versions, property-based deserialization does not check the active @JsonView when buffering certain properties. If an application deserializes attacker-controlled JSON with an active view that excludes a restricted setterless collection, the attacker can still populate that collection. The input does not specify network or local access, authentication requirements, or user interaction.
Check applications using Maven com.fasterxml.jackson.core:jackson-databind versions >=2.21.0 <2.21.4 or >=3.0.0 <3.1.4, or tools.jackson.core:jackson-databind versions >=3.0.0 <3.1.4.