CVE-2018-14721 critical CVSS 10.0

SSRF (Server-Side Request Forgery) in com.fasterxml.jackson.core:jackson-databind (CVE-2018-14721)

Summary

SSRF in com.fasterxml.jackson.core:jackson-databind (CVE-2018-14721). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 2.7.9.5 or later.

Original description

The description as published by the source.

FasterXML jackson-databind 2.x before 2.9.7 might allow remote attackers to conduct server-side request forgery (SSRF) attacks by leveraging failure to block the axis2-jaxws class from polymorphic deserialization.

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-2018-14721 has been found in com.fasterxml.jackson.core:jackson-databind.
Successful exploitation can lead to full system takeover. CVSS score: 10.0/10.
What to do: upgrade com.fasterxml.jackson.core:jackson-databind to 2.7.9.5 or later.
If unsure, ask your IT team or search "com.fasterxml.jackson.core:jackson-databind CVE-2018-14721" on the vendor's site.

CVE-2018-14721 (com.fasterxml.jackson.core:jackson-databind) — CWE-918 / CVSS v3 10.0
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 2.7.9.5 — 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

SSRF (CWE-918) 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 10.0/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 2.7.9.5.

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

Fix status by distribution

Fixed packages published by each distribution for this CVE

Debian DEBIAN-CVE-2018-14721 jackson-databind Fixed in: 2.9.8-1