This page tracks the Ubuntu fix status. The vulnerability itself is described on the main CVE page. View CVE-2018-14048 →
Categories
UBUNTU-CVE-2018-14048

Vulnerability in libpng (UBUNTU-CVE-2018-14048)

Summary

Vulnerability in libpng (UBUNTU-CVE-2018-14048). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.2.54-1ubuntu1.1+esm1 or later.

Original description

The description as published by the source.

An issue has been found in libpng 1.6.34. It is a SEGV in the function png_free_data in png.c, related to the recommended error handling for png_read_image.

Source: OSV.dev (Open Source Vulnerabilities) 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 UBUNTU-CVE-2018-14048 has been found in libpng.
Risk of unauthorized operations or information disclosure.
What to do: upgrade libpng to 1.2.54-1ubuntu1.1+esm1 or later.
If unsure, ask your IT team or search "libpng UBUNTU-CVE-2018-14048" on the vendor's site.

UBUNTU-CVE-2018-14048 (libpng)
Attack vector: remote (network-reachable) / unauthenticated
Patched: 1.2.54-1ubuntu1.1+esm1 — 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 libpng.

📍 Affected scope

Check the vendor advisory for the affected versions of libpng.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 1.2.54-1ubuntu1.1+esm1.

🛡️ 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 'libpng' . 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 'libpng' . | grep -v node_modules

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

  2. 2
    Apply patch patch
    Upgrade libpng to 1.2.54-1ubuntu1.1+esm1

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

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

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

Affected packages

Ubuntu:Pro:16.04:LTS libpng
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.2.54-1ubuntu1.1+esm1"}]}]
Ubuntu:Pro:16.04:LTS libpng1.6
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.6.20-2ubuntu0.1~esm1"}]}]
Ubuntu:Pro:18.04:LTS libpng1.6
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.6.34-1ubuntu0.18.04.2+esm3"}]}]

References

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