ALSA-2020:1577 (CVE-2017-18005)
Vulnerability from osv_almalinux – Published: 2020-04-28 08:52 – Updated: 2026-11-05 07:52 – Source websiteThe exiv2 packages provide a command line utility which can display and manipulate image metadata such as EXIF, LPTC, and JPEG comments.
The following packages have been upgraded to a later upstream version: exiv2 (0.27.2). (BZ#1651917)
Security Fix(es):
-
exiv2: infinite loop and hang in Jp2Image::readMetadata() in jp2image.cpp could lead to DoS (CVE-2019-20421)
-
exiv2: null pointer dereference in the Exiv2::DataValue::toLong function in value.cpp (CVE-2017-18005)
-
exiv2: Excessive memory allocation in Exiv2::Jp2Image::readMetadata function in jp2image.cpp (CVE-2018-4868)
-
exiv2: assertion failure in BigTiffImage::readData in bigtiffimage.cpp (CVE-2018-9303)
-
exiv2: divide by zero in BigTiffImage::printIFD in bigtiffimage.cpp (CVE-2018-9304)
-
exiv2: out of bounds read in IptcData::printStructure in iptc.c (CVE-2018-9305)
-
exiv2: OOB read in pngimage.cpp:tEXtToDataBuf() allows for crash via crafted file (CVE-2018-10772)
-
exiv2: information leak via a crafted file (CVE-2018-11037)
-
exiv2: buffer overflow in samples/geotag.cpp (CVE-2018-14338)
-
exiv2: heap-based buffer overflow in Exiv2::d2Data in types.cpp (CVE-2018-17229)
-
exiv2: heap-based buffer overflow in Exiv2::ul2Data in types.cpp (CVE-2018-17230)
-
exiv2: NULL pointer dereference in Exiv2::DataValue::copy in value.cpp leading to application crash (CVE-2018-17282)
-
exiv2: Stack overflow in CiffDirectory::readDirectory() at crwimage_int.cpp leading to denial of service (CVE-2018-17581)
-
exiv2: infinite loop in Exiv2::Image::printIFDStructure function in image.cpp (CVE-2018-18915)
-
exiv2: heap-based buffer over-read in Exiv2::IptcParser::decode in iptc.cpp (CVE-2018-19107)
-
exiv2: infinite loop in Exiv2::PsdImage::readMetadata in psdimage.cpp (CVE-2018-19108)
-
exiv2: heap-based buffer over-read in PngChunk::readRawProfile in pngchunk_int.cpp (CVE-2018-19535)
-
exiv2: NULL pointer dereference in Exiv2::isoSpeed in easyaccess.cpp (CVE-2018-19607)
-
exiv2: Heap-based buffer over-read in Exiv2::tEXtToDataBuf function resulting in a denial of service (CVE-2018-20096)
-
exiv2: Segmentation fault in Exiv2::Internal::TiffParserWorker::findPrimaryGroups function (CVE-2018-20097)
-
exiv2: Heap-based buffer over-read in Exiv2::Jp2Image::encodeJp2Header resulting in a denial of service (CVE-2018-20098)
-
exiv2: Infinite loop in Exiv2::Jp2Image::encodeJp2Header resulting in a denial of service (CVE-2018-20099)
-
exiv2: infinite recursion in Exiv2::Image::printTiffStructure in file image.cpp resulting in denial of service (CVE-2019-9143)
-
exiv2: denial of service in PngImage::readMetadata (CVE-2019-13109)
-
exiv2: integer overflow in WebPImage::decodeChunks leads to denial of service (CVE-2019-13111)
-
exiv2: uncontrolled memory allocation in PngChunk::parseChunkContent causing denial of service (CVE-2019-13112)
-
exiv2: invalid data location in CRW image file causing denial of service (CVE-2019-13113)
-
exiv2: null-pointer dereference in http.c causing denial of service (CVE-2019-13114)
-
exiv2: out of bounds read in IptcData::printStructure in iptc.c (CVE-2018-9306)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
Additional Changes:
For detailed information on changes in this release, see the AlmaLinux Release Notes linked from the References section.
| Ecosystem | Package | Version |
|---|---|---|
| AlmaLinux:8 | exiv2-devel |
Affected: < 0.27.2-5.el8 (ecosystem)
|
| AlmaLinux:8 | exiv2-doc |
Affected: < 0.27.2-5.el8 (ecosystem)
|
| AlmaLinux:8 | gegl |
Affected: < 0.2.0-39.el8 (ecosystem)
|
| AlmaLinux:8 | gnome-color-manager |
Affected: < 3.28.0-3.el8 (ecosystem)
|
| AlmaLinux:8 | libgexiv2 |
Affected: < 0.10.8-4.el8 (ecosystem)
|
| AlmaLinux:8 | libgexiv2-devel |
Affected: < 0.10.8-4.el8 (ecosystem)
|
{
"affected": [
{
"package": {
"ecosystem": "AlmaLinux:8",
"name": "exiv2-devel"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.27.2-5.el8"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "AlmaLinux:8",
"name": "exiv2-doc"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.27.2-5.el8"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "AlmaLinux:8",
"name": "gegl"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.2.0-39.el8"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "AlmaLinux:8",
"name": "gnome-color-manager"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "3.28.0-3.el8"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "AlmaLinux:8",
"name": "libgexiv2"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.10.8-4.el8"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "AlmaLinux:8",
"name": "libgexiv2-devel"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.10.8-4.el8"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"details": "The exiv2 packages provide a command line utility which can display and manipulate image metadata such as EXIF, LPTC, and JPEG comments.\n\nThe following packages have been upgraded to a later upstream version: exiv2 (0.27.2). (BZ#1651917)\n\nSecurity Fix(es):\n\n* exiv2: infinite loop and hang in Jp2Image::readMetadata() in jp2image.cpp could lead to DoS (CVE-2019-20421)\n\n* exiv2: null pointer dereference in the Exiv2::DataValue::toLong function in value.cpp (CVE-2017-18005)\n\n* exiv2: Excessive memory allocation in Exiv2::Jp2Image::readMetadata function in jp2image.cpp (CVE-2018-4868)\n\n* exiv2: assertion failure in BigTiffImage::readData in bigtiffimage.cpp (CVE-2018-9303)\n\n* exiv2: divide by zero in BigTiffImage::printIFD in bigtiffimage.cpp (CVE-2018-9304)\n\n* exiv2: out of bounds read in IptcData::printStructure in iptc.c (CVE-2018-9305)\n\n* exiv2: OOB read in pngimage.cpp:tEXtToDataBuf() allows for crash via crafted file (CVE-2018-10772)\n\n* exiv2: information leak via a crafted file (CVE-2018-11037)\n\n* exiv2: buffer overflow in samples/geotag.cpp (CVE-2018-14338)\n\n* exiv2: heap-based buffer overflow in Exiv2::d2Data in types.cpp (CVE-2018-17229)\n\n* exiv2: heap-based buffer overflow in Exiv2::ul2Data in types.cpp (CVE-2018-17230)\n\n* exiv2: NULL pointer dereference in Exiv2::DataValue::copy in value.cpp leading to application crash (CVE-2018-17282)\n\n* exiv2: Stack overflow in CiffDirectory::readDirectory() at crwimage_int.cpp leading to denial of service (CVE-2018-17581)\n\n* exiv2: infinite loop in Exiv2::Image::printIFDStructure function in image.cpp (CVE-2018-18915)\n\n* exiv2: heap-based buffer over-read in Exiv2::IptcParser::decode in iptc.cpp (CVE-2018-19107)\n\n* exiv2: infinite loop in Exiv2::PsdImage::readMetadata in psdimage.cpp (CVE-2018-19108)\n\n* exiv2: heap-based buffer over-read in PngChunk::readRawProfile in pngchunk_int.cpp (CVE-2018-19535)\n\n* exiv2: NULL pointer dereference in Exiv2::isoSpeed in easyaccess.cpp (CVE-2018-19607)\n\n* exiv2: Heap-based buffer over-read in Exiv2::tEXtToDataBuf function resulting in a denial of service (CVE-2018-20096)\n\n* exiv2: Segmentation fault in Exiv2::Internal::TiffParserWorker::findPrimaryGroups function (CVE-2018-20097)\n\n* exiv2: Heap-based buffer over-read in Exiv2::Jp2Image::encodeJp2Header resulting in a denial of service (CVE-2018-20098)\n\n* exiv2: Infinite loop in Exiv2::Jp2Image::encodeJp2Header resulting in a denial of service (CVE-2018-20099)\n\n* exiv2: infinite recursion in Exiv2::Image::printTiffStructure in file image.cpp resulting in denial of service (CVE-2019-9143)\n\n* exiv2: denial of service in PngImage::readMetadata (CVE-2019-13109)\n\n* exiv2: integer overflow in WebPImage::decodeChunks leads to denial of service (CVE-2019-13111)\n\n* exiv2: uncontrolled memory allocation in PngChunk::parseChunkContent causing denial of service (CVE-2019-13112)\n\n* exiv2: invalid data location in CRW image file causing denial of service (CVE-2019-13113)\n\n* exiv2: null-pointer dereference in http.c causing denial of service (CVE-2019-13114)\n\n* exiv2: out of bounds read in IptcData::printStructure in iptc.c (CVE-2018-9306)\n\nFor more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.\n\nAdditional Changes:\n\nFor detailed information on changes in this release, see the AlmaLinux Release Notes linked from the References section.",
"id": "ALSA-2020:1577",
"modified": "2026-11-05T07:52:15Z",
"published": "2020-04-28T08:52:31Z",
"references": [
{
"type": "ADVISORY",
"url": "https://access.redhat.com/errata/RHSA-2020:1577"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/1531171"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/1531724"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/1566725"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/1566731"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/1566735"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/1566737"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/1579544"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/1594627"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/1609396"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/1632481"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/1632484"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/1632490"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/1635045"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/1646555"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/1649094"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/1649101"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/1651917"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/1656187"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/1656195"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/1660423"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/1660424"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/1660425"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/1660426"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/1684381"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/1728484"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/1728488"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/1728490"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/1728492"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/1728494"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/1757444"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/1757445"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/1767748"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/1800472"
},
{
"type": "ADVISORY",
"url": "https://errata.almalinux.org/8/ALSA-2020-1577.html"
},
{
"type": "REPORT",
"url": "https://vulners.com/cve/CVE-2017-18005"
},
{
"type": "REPORT",
"url": "https://vulners.com/cve/CVE-2018-10772"
},
{
"type": "REPORT",
"url": "https://vulners.com/cve/CVE-2018-11037"
},
{
"type": "REPORT",
"url": "https://vulners.com/cve/CVE-2018-14338"
},
{
"type": "REPORT",
"url": "https://vulners.com/cve/CVE-2018-17229"
},
{
"type": "REPORT",
"url": "https://vulners.com/cve/CVE-2018-17230"
},
{
"type": "REPORT",
"url": "https://vulners.com/cve/CVE-2018-17282"
},
{
"type": "REPORT",
"url": "https://vulners.com/cve/CVE-2018-17581"
},
{
"type": "REPORT",
"url": "https://vulners.com/cve/CVE-2018-18915"
},
{
"type": "REPORT",
"url": "https://vulners.com/cve/CVE-2018-19107"
},
{
"type": "REPORT",
"url": "https://vulners.com/cve/CVE-2018-19108"
},
{
"type": "REPORT",
"url": "https://vulners.com/cve/CVE-2018-19535"
},
{
"type": "REPORT",
"url": "https://vulners.com/cve/CVE-2018-19607"
},
{
"type": "REPORT",
"url": "https://vulners.com/cve/CVE-2018-20096"
},
{
"type": "REPORT",
"url": "https://vulners.com/cve/CVE-2018-20097"
},
{
"type": "REPORT",
"url": "https://vulners.com/cve/CVE-2018-20098"
},
{
"type": "REPORT",
"url": "https://vulners.com/cve/CVE-2018-20099"
},
{
"type": "REPORT",
"url": "https://vulners.com/cve/CVE-2018-4868"
},
{
"type": "REPORT",
"url": "https://vulners.com/cve/CVE-2018-9303"
},
{
"type": "REPORT",
"url": "https://vulners.com/cve/CVE-2018-9304"
},
{
"type": "REPORT",
"url": "https://vulners.com/cve/CVE-2018-9305"
},
{
"type": "REPORT",
"url": "https://vulners.com/cve/CVE-2018-9306"
},
{
"type": "REPORT",
"url": "https://vulners.com/cve/CVE-2019-13109"
},
{
"type": "REPORT",
"url": "https://vulners.com/cve/CVE-2019-13111"
},
{
"type": "REPORT",
"url": "https://vulners.com/cve/CVE-2019-13112"
},
{
"type": "REPORT",
"url": "https://vulners.com/cve/CVE-2019-13113"
},
{
"type": "REPORT",
"url": "https://vulners.com/cve/CVE-2019-13114"
},
{
"type": "REPORT",
"url": "https://vulners.com/cve/CVE-2019-20421"
},
{
"type": "REPORT",
"url": "https://vulners.com/cve/CVE-2019-9143"
}
],
"related": [
"CVE-2017-18005",
"CVE-2018-10772",
"CVE-2018-11037",
"CVE-2018-14338",
"CVE-2018-17229",
"CVE-2018-17230",
"CVE-2018-17282",
"CVE-2018-17581",
"CVE-2018-18915",
"CVE-2018-19107",
"CVE-2018-19108",
"CVE-2018-19535",
"CVE-2018-19607",
"CVE-2018-20096",
"CVE-2018-20097",
"CVE-2018-20098",
"CVE-2018-20099",
"CVE-2018-4868",
"CVE-2018-9303",
"CVE-2018-9304",
"CVE-2018-9305",
"CVE-2018-9306",
"CVE-2019-13109",
"CVE-2019-13111",
"CVE-2019-13112",
"CVE-2019-13113",
"CVE-2019-13114",
"CVE-2019-20421",
"CVE-2019-9143"
],
"schema_version": "1.7.0",
"summary": "Moderate: exiv2 security, bug fix, and enhancement update",
"upstream": [
"CVE-2017-18005",
"CVE-2018-10772",
"CVE-2018-11037",
"CVE-2018-14338",
"CVE-2018-17229",
"CVE-2018-17230",
"CVE-2018-17282",
"CVE-2018-17581",
"CVE-2018-18915",
"CVE-2018-19107",
"CVE-2018-19108",
"CVE-2018-19535",
"CVE-2018-19607",
"CVE-2018-20096",
"CVE-2018-20097",
"CVE-2018-20098",
"CVE-2018-20099",
"CVE-2018-4868",
"CVE-2018-9303",
"CVE-2018-9304",
"CVE-2018-9305",
"CVE-2018-9306",
"CVE-2019-13109",
"CVE-2019-13111",
"CVE-2019-13112",
"CVE-2019-13113",
"CVE-2019-13114",
"CVE-2019-20421",
"CVE-2019-9143"
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.