CVE-2020-9546 critical CVSS 9.8

Unsafe Deserialization in com.fasterxml.jackson.core:jackson-databind (CVE-2020-9546)

Summary

Vulnerability in com.fasterxml.jackson.core:jackson-databind (CVE-2020-9546). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 2.9.10.4 or later.

Original description

The description as published by the source.

FasterXML jackson-databind 2.x before 2.9.10.4 mishandles the interaction between serialization gadgets and typing, related to org.apache.hadoop.shaded.com.zaxxer.hikari.HikariConfig (aka shaded hikari-config).

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2020-9546 has been found in com.fasterxml.jackson.core:jackson-databind.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: upgrade com.fasterxml.jackson.core:jackson-databind to 2.9.10.4 or later.
If unsure, ask your IT team or search "com.fasterxml.jackson.core:jackson-databind CVE-2020-9546" on the vendor's site.

CVE-2020-9546 (com.fasterxml.jackson.core:jackson-databind) — CWE-502 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 2.9.10.4 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Unsafe deserialization (CWE-502) exists in com.fasterxml.jackson.core:jackson-databind.

📍 Affected scope

Check the vendor advisory for the affected versions of com.fasterxml.jackson.core:jackson-databind.

🔥 Severity

Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 2.9.10.4.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
Audit SBOM/dependencies for affected components.
```
資産台帳・SBOM・依存マニフェストで com.fasterxml.jackson.core:jackson-databind を使っているサービスとバージョンを洗い出す。
2
Apply patch patch
```
Upgrade com.fasterxml.jackson.core:jackson-databind to 2.9.10.4
```
ステージング環境で 2.9.10.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Maven com.fasterxml.jackson.core:jackson-databind

[{"type":"ECOSYSTEM","events":[{"introduced":"2.9.0"},{"fixed":"2.9.10.4"}]}]

Summary

Original description

Auto-generated summary

Response actions

Affected packages

References