Vulnerability in Dave Gamble cJSON (CVE-2018-1000216)

Summary

Vulnerability in Dave Gamble cJSON (CVE-2018-1000216). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 1.7.3 or later.

Original description

The description as published by the source.

Dave Gamble cJSON version 1.7.2 and earlier contains a CWE-415: Double Free vulnerability in cJSON library that can result in Possible crash or RCE. This attack appear to be exploitable via Attacker must be able to force victim to print JSON data, depending on how cJSON library is used this could be either local or over a network. This vulnerability appears to have been fixed in 1.7.3.

Source: OSV.dev (Open Source Vulnerabilities) NVD 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-1000216 has been found in Dave Gamble cJSON.
Successful exploitation can lead to full system takeover.
What to do: upgrade Dave Gamble cJSON to 1.7.3 or later.
If unsure, ask your IT team or search "Dave Gamble cJSON CVE-2018-1000216" on the vendor's site.

CVE-2018-1000216 (Dave Gamble cJSON)
Attack vector: remote (network-reachable) / unauthenticated
Patched: 1.7.3 — 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 (unclassified) exists in Dave Gamble cJSON.

📍 Affected scope

Check the vendor advisory for the affected versions of Dave Gamble cJSON.

🔥 Severity

Severity: ?. Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 1.7.3.

🛡️ 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・依存マニフェストで Dave Gamble cJSON を使っているサービスとバージョンを洗い出す。
2
Apply patch patch
```
Upgrade Dave Gamble cJSON to 1.7.3
```
ステージング環境で 1.7.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

References

report github.com