Unsafe Deserialization in com.fasterxml.jackson.core:jackson-databind (CVE-2020-10650)
Summary
Vulnerability in com.fasterxml.jackson.core:jackson-databind (CVE-2020-10650). 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.
A deserialization flaw was discovered in jackson-databind through 2.9.10.4. It could allow an unauthenticated user to perform code execution via ignite-jta or quartz-core: org.apache.ignite.cache.jta.jndi.CacheJndiTmLookup, org.apache.ignite.cache.jta.jndi.CacheJndiTmFactory, and org.quartz.utils.JNDIConnectionProvider.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
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-10650 has been found in com.fasterxml.jackson.core:jackson-databind.
Successful exploitation can lead to full system takeover.
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-10650" on the vendor's site.
CVE-2020-10650 (com.fasterxml.jackson.core:jackson-databind) — CWE-502
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.
Unsafe deserialization (CWE-502) exists in com.fasterxml.jackson.core:jackson-databind.
Check the vendor advisory for the affected versions of com.fasterxml.jackson.core:jackson-databind.
Severity: ?. Successful exploitation can lead to full system takeover.
Update to 2.9.10.4.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで com.fasterxml.jackson.core:jackson-databind を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade com.fasterxml.jackson.core:jackson-databind to 2.9.10.4ステージング環境で 2.9.10.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2020-10650 jackson-databind Fixed in: 2.11.1-1
- Ubuntu UBUNTU-CVE-2020-10650 jackson-databind
References
- advisory nvd.nist.gov
- advisory lists.debian.org
- advisory github.com
- advisory security.netapp.com
- package github.com
- patch github.com
- patch github.com
- patch oracle.com
- patch oracle.com
- report medium.com
- web github.com
- web github.com
- web medium.com
- web security.netapp.com