Skip to content
Fencer Vulns
medium 6.5

CVE-2019-13504 json

There is an out-of-bounds read in Exiv2::MrwImage::readMetadata in mrwimage.cpp in Exiv2 through 0.27.2.

published 2019-07-11 7 y ago modified 2026-06-17 4 mo ago also EUVD-2019-4961

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

Summary

There is an out-of-bounds read in Exiv2::MrwImage::readMetadata in mrwimage.cpp in Exiv2 through 0.27.2.

Patch / fix

  • exiv2 Debian 14, Debian 13, Debian 12 0.27.2-6

debian advisories DEBIAN-CVE-2019-13504

  • exiv2 CBL-Mariner 2.0 0.27.5-1

azure linux advisories AZL-7203

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

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-2019-13504 updated cvss 6.5

exiv2: out-of-bounds read in Exiv2::MrwImage::readMetadata in mrwimage.cpp

  • Red Hat Enterprise Linux 6 exiv2, exiv2-libs
    affected: no fix planned “Out of support scope”
  • Red Hat Enterprise Linux 7 exiv2, exiv2-libs Red Hat Enterprise Linux 8 exiv2, exiv2-libs
    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.39% chance of exploitation in the next 30 days, higher than 84% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • github.com https://github.com/Exiv2/exiv2/pull/943 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:N/I:N/A:H
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:N/A:P

Classification

Weakness

References

Sources

Fencer Vulns 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.