Categories
CVE-2017-14491 critical CVSS 9.8

Out-of-Bounds Write in platform/external/dnsmasq (CVE-2017-14491)

Summary

Out-of-bounds write in platform/external/dnsmasq (CVE-2017-14491). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 11:2021-03-01 or later.

Original description

The description as published by the source.

In do_rfc1035_name of util.c, there is a possible out of bounds write due to a missing bounds check. This could lead to remote code execution when processing a malicious DNS server response with no additional execution privileges needed. User interaction is not needed for exploitation.

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-2017-14491 has been found in platform/external/dnsmasq.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: upgrade platform/external/dnsmasq to 11:2021-03-01 or later.
If unsure, ask your IT team or search "platform/external/dnsmasq CVE-2017-14491" on the vendor's site.

CVE-2017-14491 (platform/external/dnsmasq) — CWE-787 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 11:2021-03-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

Out-of-bounds write (CWE-787) exists in platform/external/dnsmasq.

📍 Affected scope

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

🔥 Severity

Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 11:2021-03-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/dnsmasq' . 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/dnsmasq' . | grep -v node_modules

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

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

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

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

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

Affected packages

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

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

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