← Back
CVE-2020-15999
CISA KEV
high
[KEV] Out-of-Bounds Write in Google platform/external/freetype (CVE-2020-15999)
Summary
out-of-bounds write in Google platform/external/freetype (CVE-2020-15999). Risk of unauthorized operations or information disclosure. Listed in CISA KEV — actively exploited. Mitigation: upgrade to `11:2021-01-01` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2020-15999** has been found in Google platform/external/freetype.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
Note: CISA has officially confirmed this is **actively exploited in the wild**. Treat it with elevated urgency.
What to do: upgrade Google platform/external/freetype to **11:2021-01-01** or later.
If unsure, ask your IT team or search "Google platform/external/freetype CVE-2020-15999" on the vendor's site.
CVE-2020-15999 (Google platform/external/freetype) — CWE-787 /
Patched: `11:2021-01-01` — apply immediately
Listed in CISA KEV — actively exploited, treat as top priority.
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
**out-of-bounds write** (CWE-787) exists in Google platform/external/freetype.
📍 Affected scope
Google platform/external/freetype — .
🔥 Severity
Severity: High. Risk of unauthorized operations or information disclosure **Listed in CISA KEV** — actively exploited in the wild, treat as top priority.
🔧 How to fix
Update to **11:2021-01-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/freetype' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'platform/external/freetype' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `platform/external/freetype` を grep し、稼働しているサービス・バージョンを把握する。
-
4Consider incident declaration escalate
Notify SOC / on-callCISA KEV登録済 = 実環境で悪用が観測されている。Step 3 で兆候があればインシデント対応宣言、無くてもパッチ適用までWAF強化を最優先で。
-
6Apply patch patch
Upgrade platform/external/freetype to 11:2021-01-01ステージング環境で 11:2021-01-01 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Android
platform/external/freetype
[{"type":"ECOSYSTEM","events":[{"introduced":"11:0"},{"fixed":"11:2021-01-01"}]}]