Categories
CVE-2017-16942 medium CVSS 6.5

Vulnerability in Libsndfile Project (CVE-2017-16942)

Summary

Vulnerability in Libsndfile Project (CVE-2017-16942). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.0.26 or later.

Original description

The description as published by the source.

In libsndfile 1.0.25 (fixed in 1.0.26), a divide-by-zero error exists in the function wav_w64_read_fmt_chunk() in wav_w64.c, which may lead to DoS when playing a crafted audio file.

Source: NIST National Vulnerability Database NVD

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-16942 has been found in Libsndfile Project.
Risk of unauthorized operations or information disclosure. CVSS score: 6.5/10.
What to do: upgrade Libsndfile Project to 1.0.26 or later.
If unsure, ask your IT team or search "Libsndfile Project CVE-2017-16942" on the vendor's site.

CVE-2017-16942 (Libsndfile Project) — CWE-369 / CVSS v3 6.5
Attack vector: remote (network-reachable) / unauthenticated
Patched: 1.0.26 — 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 (CWE-369) exists in Libsndfile Project.

📍 Affected scope

Check the vendor advisory for the affected versions of Libsndfile Project.

🔥 Severity

Severity: Medium (CVSS 6.5/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 1.0.26.

🛡️ 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. 1
    Identify exposure identify
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで Libsndfile Project を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch
    Upgrade Libsndfile Project to 1.0.26

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

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

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

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