Skip to content
Fencer Intel
medium 6.5

CVE-2018-11439 json

The TagLib::Ogg::FLAC::File::scan function in oggflacfile.cpp in TagLib 1.11.1 allows remote attackers to cause information disclosure (hea…

published 8y ago modified 4mo ago also EUVD-2018-3470

cvss
6.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.9%
EPSS 2.9% chance of exploitation in 30 days, percentile 87%
public exploits
0
none known

Summary

The TagLib::Ogg::FLAC::File::scan function in oggflacfile.cpp in TagLib 1.11.1 allows remote attackers to cause information disclosure (heap-based buffer over-read) via a crafted audio file.

Patch / fix

  • taglib Debian 14, Debian 13, Debian 12 1.11.1+dfsg.1-0.3

debian advisories DEBIAN-CVE-2018-11439

  • taglib RHEL 7 1.8-8.20130218git.el7

red hat advisories RHSA-2020:1175

  • taglib SLES for SAP 12 SP5, SLES 12 SP5, SLE Workstation Extension 12 SP5 +1 more 1.9.1-3.4.18
  • taglib SLE Module for Desktop Applications 15 SP1, SLE Module for Basesystem 15 SP1 1.11.1-4.3.62

suse advisories SUSE-SU-2020:2968-1SUSE-SU-2019:1374-2

  • taglib openSUSE Tumbleweed 1.12-1.3

opensuse advisories openSUSE-SU-2024:11421-1

  • taglib Alpine 3.24, Alpine 3.23, Alpine 3.22 +12 more 1.11.1-r2

alpine advisories ALPINE-CVE-2018-11439

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • taglib CBL-Mariner 2.0 1.13.1-1

azure linux advisories AZL-7380

Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT

Is CVE-2018-11439 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2018-11439 updated cvss 3.3

taglib: heap-based buffer over-read via a crafted audio file

  • Red Hat Enterprise Linux 6 taglib
    affected: no fix planned “Will not fix”
  • Red Hat Enterprise Linux Client (v. 7) taglib 1.8-8.20130218git.el7 Red Hat Enterprise Linux Client Optional (v. 7) taglib-doc 1.8-8.20130218git.el7, taglib-devel 1.8-8.20130218git.el7, taglib-debuginfo 1.8-8.20130218git.el7 Red Hat Enterprise Linux ComputeNode (v. 7) taglib 1.8-8.20130218git.el7 Red Hat Enterprise Linux ComputeNode Optional (v. 7) taglib-doc 1.8-8.20130218git.el7, taglib-devel 1.8-8.20130218git.el7, taglib-debuginfo 1.8-8.20130218git.el7 Red Hat Enterprise Linux Server (v. 7) taglib 1.8-8.20130218git.el7 Red Hat Enterprise Linux Server Optional (v. 7) taglib-doc 1.8-8.20130218git.el7, taglib-devel 1.8-8.20130218git.el7, taglib-debuginfo 1.8-8.20130218git.el7
    +2 more products
    Red Hat Enterprise Linux Workstation (v. 7) taglib 1.8-8.20130218git.el7 Red Hat Enterprise Linux Workstation Optional (v. 7) taglib-doc 1.8-8.20130218git.el7, taglib-devel 1.8-8.20130218git.el7, taglib-debuginfo 1.8-8.20130218git.el7
    fixed: vendor fix RHSA-2020:1175
  • Red Hat Enterprise Linux 8 taglib Red Hat Enterprise Linux 9 taglib
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.93% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • seclists.org http://seclists.org/fulldisclosure/2018/May/49 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:P/I:N/A:N

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.