Categories
CVE-2020-13871 high CVSS 7.5

Use-After-Free in platform/external/sqlite (CVE-2020-13871)

Summary

Vulnerability in platform/external/sqlite (CVE-2020-13871). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 11:2021-11-01 or later.

Original description

The description as published by the source.

SQLite 3.32.2 has a use-after-free in resetAccumulator in select.c because the parse tree rewrite for window functions is too late.

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-13871 has been found in platform/external/sqlite.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade platform/external/sqlite to 11:2021-11-01 or later.
If unsure, ask your IT team or search "platform/external/sqlite CVE-2020-13871" on the vendor's site.

CVE-2020-13871 (platform/external/sqlite) — CWE-416 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 11:2021-11-01 — 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

Use-after-free (CWE-416) exists in platform/external/sqlite.

📍 Affected scope

Check the vendor advisory for the affected versions of platform/external/sqlite.

🔥 Severity

Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 11:2021-11-01.

🛡️ 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. Run grep -r 'platform/external/sqlite' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

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

  1. 1
    Identify exposure identify
    grep -r 'platform/external/sqlite' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で platform/external/sqlite を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade platform/external/sqlite to 11:2021-11-01

    ステージング環境で 11:2021-11-01 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Android platform/external/sqlite
[{"type":"ECOSYSTEM","events":[{"introduced":"11:0"},{"fixed":"11:2021-11-01"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details