CVE-2020-25649 high CVSS 7.5

XXE (XML External Entity) in com.fasterxml.jackson.core:jackson-databind (CVE-2020-25649)

Summary

Vulnerability in com.fasterxml.jackson.core:jackson-databind (CVE-2020-25649). Data can be tampered with by attackers. Mitigation: upgrade to 2.10.5.1 or later.

Original description

The description as published by the source.

A flaw was found in FasterXML Jackson Databind, where it did not have entity expansion secured properly. This flaw allows vulnerability to XML external entity (XXE) attacks. The highest threat from this vulnerability is data integrity.

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-25649 has been found in com.fasterxml.jackson.core:jackson-databind.
Data can be tampered with by attackers. CVSS score: 7.5/10.
What to do: upgrade com.fasterxml.jackson.core:jackson-databind to 2.10.5.1 or later.
If unsure, ask your IT team or search "com.fasterxml.jackson.core:jackson-databind CVE-2020-25649" on the vendor's site.

CVE-2020-25649 (com.fasterxml.jackson.core:jackson-databind) — CWE-611 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 2.10.5.1 — 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

A vulnerability (CWE-611) 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: High (CVSS 7.5/10). Data can be tampered with by attackers.

🔧 How to fix

Update to 2.10.5.1.

🛡️ 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.10.5.1
```
ステージング環境で 2.10.5.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
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.10.0.0"},{"fixed":"2.10.5.1"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

Debian DEBIAN-CVE-2020-25649 jackson-databind Fixed in: 2.11.1-1