Jackson-databind Vulnerability: @JsonIgnore Bypassed with PropertyNamingStrategy
An early warning has been issued regarding a vulnerability in jackson-databind that reportedly allows bypassing the @JsonIgnore annotation on Record properties using a PropertyNamingStrategy. This issue may affect systems utilizing affected versions of jackson-databind.
What happened
An early warning has been issued for a vulnerability in jackson-databind, tracked under GHSA-3PJW-73GF-8QR5. This vulnerability appears to allow the bypassing of the @JsonIgnore annotation on Record properties through the use of a PropertyNamingStrategy. As a result, untrusted clients may be able to set internal components of the Record, potentially leading to security risks.
The affected versions of jackson-databind are those within the ranges >=2.15.0,<2.18.8, >=2.19.0,<2.21.4, and >=3.0.0,<3.1.4. It is under investigation whether this vulnerability has been actively exploited in the wild. Professional software engineers are advised to assess their systems for exposure to this vulnerability.
As a recommended action, it is advised to upgrade to jackson-databind version 2.18.8, 2.21.4, or 3.1.4 as appropriate. Further details and confirmations should be sought from the primary sources, particularly the GitHub Security Advisory linked above.
How 0Day mitigates this
jackson-databind is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.