OESA-2022-1869 (CVE-2022-2867)

Vulnerability from osv_openeuler – Published: 2022-08-26 11:05 – Updated: 2026-08-06 11:05 – Source website
VLAI
Summary
libtiff security update
Details

Security Fix(es):

libtiff's tiffcrop utility has a uint32_t underflow that can lead to out of bounds read and write. An attacker who supplies a crafted file to tiffcrop (likely via tricking a user to run tiffcrop on it with certain parameters) could cause a crash or in some cases, further exploitation.(CVE-2022-2867)

libtiff's tiffcrop utility has a improper input validation flaw that can lead to out of bounds read and ultimately cause a crash if an attacker is able to supply a crafted file to tiffcrop.(CVE-2022-2868)

libtiff's tiffcrop tool has a uint32_t underflow which leads to out of bounds read and write in the extractContigSamples8bits routine. An attacker who supplies a crafted file to tiffcrop could trigger this flaw, most likely by tricking a user into opening the crafted file with tiffcrop. Triggering this flaw could cause a crash or potentially further exploitation.(CVE-2022-2869)

Severity
8.8 (High)
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
References
To clipboard 

{
  "affected": [
    {
      "ecosystem_specific": {
        "aarch64": [
          "libtiff-4.3.0-3.oe1.aarch64.rpm",
          "libtiff-debuginfo-4.3.0-3.oe1.aarch64.rpm",
          "libtiff-debugsource-4.3.0-3.oe1.aarch64.rpm",
          "libtiff-devel-4.3.0-3.oe1.aarch64.rpm"
        ],
        "noarch": [
          "libtiff-help-4.3.0-3.oe1.noarch.rpm"
        ],
        "src": [
          "libtiff-4.3.0-3.oe1.src.rpm"
        ],
        "x86_64": [
          "libtiff-debugsource-4.3.0-3.oe1.x86_64.rpm",
          "libtiff-devel-4.3.0-3.oe1.x86_64.rpm",
          "libtiff-4.3.0-3.oe1.x86_64.rpm",
          "libtiff-debuginfo-4.3.0-3.oe1.x86_64.rpm"
        ]
      },
      "package": {
        "ecosystem": "openEuler:20.03-LTS-SP1",
        "name": "libtiff",
        "purl": "pkg:rpm/openEuler/libtiff\u0026distro=openEuler-20.03-LTS-SP1"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "4.3.0-3.oe1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "aarch64": [
          "libtiff-devel-4.3.0-3.oe1.aarch64.rpm",
          "libtiff-4.3.0-3.oe1.aarch64.rpm",
          "libtiff-debugsource-4.3.0-3.oe1.aarch64.rpm",
          "libtiff-debuginfo-4.3.0-3.oe1.aarch64.rpm"
        ],
        "noarch": [
          "libtiff-help-4.3.0-3.oe1.noarch.rpm"
        ],
        "src": [
          "libtiff-4.3.0-3.oe1.src.rpm"
        ],
        "x86_64": [
          "libtiff-devel-4.3.0-3.oe1.x86_64.rpm",
          "libtiff-4.3.0-3.oe1.x86_64.rpm",
          "libtiff-debugsource-4.3.0-3.oe1.x86_64.rpm",
          "libtiff-debuginfo-4.3.0-3.oe1.x86_64.rpm"
        ]
      },
      "package": {
        "ecosystem": "openEuler:20.03-LTS-SP3",
        "name": "libtiff",
        "purl": "pkg:rpm/openEuler/libtiff\u0026distro=openEuler-20.03-LTS-SP3"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "4.3.0-3.oe1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "aarch64": [
          "libtiff-tools-4.3.0-17.oe2203.aarch64.rpm",
          "libtiff-devel-4.3.0-17.oe2203.aarch64.rpm",
          "libtiff-debugsource-4.3.0-17.oe2203.aarch64.rpm",
          "libtiff-debuginfo-4.3.0-17.oe2203.aarch64.rpm",
          "libtiff-4.3.0-17.oe2203.aarch64.rpm",
          "libtiff-static-4.3.0-17.oe2203.aarch64.rpm"
        ],
        "noarch": [
          "libtiff-help-4.3.0-17.oe2203.noarch.rpm"
        ],
        "src": [
          "libtiff-4.3.0-17.oe2203.src.rpm"
        ],
        "x86_64": [
          "libtiff-devel-4.3.0-17.oe2203.x86_64.rpm",
          "libtiff-debugsource-4.3.0-17.oe2203.x86_64.rpm",
          "libtiff-4.3.0-17.oe2203.x86_64.rpm",
          "libtiff-debuginfo-4.3.0-17.oe2203.x86_64.rpm",
          "libtiff-tools-4.3.0-17.oe2203.x86_64.rpm",
          "libtiff-static-4.3.0-17.oe2203.x86_64.rpm"
        ]
      },
      "package": {
        "ecosystem": "openEuler:22.03-LTS",
        "name": "libtiff",
        "purl": "pkg:rpm/openEuler/libtiff\u0026distro=openEuler-22.03-LTS"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "4.3.0-17.oe2203"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "database_specific": {
    "severity": "High"
  },
  "details": "\r\n\r\nSecurity Fix(es):\r\n\r\nlibtiff\u0026apos;s tiffcrop utility has a uint32_t underflow that can lead to out of bounds read and write. An attacker who supplies a crafted file to tiffcrop (likely via tricking a user to run tiffcrop on it with certain parameters) could cause a crash or in some cases, further exploitation.(CVE-2022-2867)\r\n\r\nlibtiff\u0026apos;s tiffcrop utility has a improper input validation flaw that can lead to out of bounds read and ultimately cause a crash if an attacker is able to supply a crafted file to tiffcrop.(CVE-2022-2868)\r\n\r\nlibtiff\u0026apos;s tiffcrop tool has a uint32_t underflow which leads to out of bounds read and write in the extractContigSamples8bits routine. An attacker who supplies a crafted file to tiffcrop could trigger this flaw, most likely by tricking a user into opening the crafted file with tiffcrop. Triggering this flaw could cause a crash or potentially further exploitation.(CVE-2022-2869)",
  "id": "OESA-2022-1869",
  "modified": "2026-08-06T11:05:08Z",
  "published": "2022-08-26T11:05:08Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2022-1869"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2022-2867"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2022-2868"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2022-2869"
    }
  ],
  "schema_version": "1.7.2",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ],
  "summary": "libtiff security update",
  "upstream": [
    "CVE-2022-2867",
    "CVE-2022-2868",
    "CVE-2022-2869"
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




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.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

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

JSON

Loading timeline…




    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.