pysec-2018-132
Vulnerability from pysec
Published
2018-06-13 11:29
Modified
2024-11-21 14:22
Details

Exiv2 0.26 has an integer overflow in the LoaderExifJpeg class in preview.cpp, leading to an out-of-bounds read in Exiv2::MemIo::read in basicio.cpp.

Impacted products
Name purl
exiv2 pkg:pypi/exiv2
Aliases



{
   affected: [
      {
         package: {
            ecosystem: "PyPI",
            name: "exiv2",
            purl: "pkg:pypi/exiv2",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "0",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
         versions: [
            "0.1",
            "0.11.0",
            "0.11.1",
            "0.11.2",
            "0.11.3",
            "0.12.0",
            "0.12.1",
            "0.13.0",
            "0.13.1",
            "0.13.2",
            "0.14.0",
            "0.14.1",
            "0.15.0",
            "0.16.0",
            "0.16.1",
            "0.16.2",
            "0.16.2.post1",
            "0.16.3",
            "0.16.3.post1",
            "0.17.0",
            "0.17.1",
            "0.2",
            "0.3",
            "0.3.1",
         ],
      },
   ],
   aliases: [
      "CVE-2018-12265",
   ],
   details: "Exiv2 0.26 has an integer overflow in the LoaderExifJpeg class in preview.cpp, leading to an out-of-bounds read in Exiv2::MemIo::read in basicio.cpp.",
   id: "PYSEC-2018-132",
   modified: "2024-11-21T14:22:48.43262Z",
   published: "2018-06-13T11:29:00Z",
   references: [
      {
         type: "EVIDENCE",
         url: "https://github.com/TeamSeri0us/pocs/blob/master/exiv2/1-out-of-read-Poc",
      },
      {
         type: "WEB",
         url: "https://github.com/TeamSeri0us/pocs/blob/master/exiv2/1-out-of-read-Poc",
      },
      {
         type: "EVIDENCE",
         url: "https://github.com/Exiv2/exiv2/issues/365",
      },
      {
         type: "REPORT",
         url: "https://github.com/Exiv2/exiv2/issues/365",
      },
      {
         type: "WEB",
         url: "https://lists.debian.org/debian-lts-announce/2018/06/msg00010.html",
      },
      {
         type: "ADVISORY",
         url: "https://www.debian.org/security/2018/dsa-4238",
      },
      {
         type: "WEB",
         url: "https://usn.ubuntu.com/3700-1/",
      },
      {
         type: "ADVISORY",
         url: "https://security.gentoo.org/glsa/201811-14",
      },
      {
         type: "ADVISORY",
         url: "https://access.redhat.com/errata/RHSA-2019:2101",
      },
      {
         type: "WEB",
         url: "http://lists.opensuse.org/opensuse-security-announce/2020-04/msg00009.html",
      },
   ],
   severity: [
      {
         score: "CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
         type: "CVSS_V3",
      },
   ],
   withdrawn: "2024-11-22T04:37:04Z",
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.