ghsa-4mq5-mj59-qq9c
Vulnerability from github
Published
2019-08-06 01:43
Modified
2021-05-05 22:55
Severity ?
6.5 (Medium) - CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
Summary
Allocation of Resources Without Limits or Throttling in Apache Tika
Details

In Apache Tika 1.19 to 1.21, a carefully crafted 2003ml or 2006ml file could consume all available SAXParsers in the pool and lead to very long hangs. Apache Tika users should upgrade to 1.22 or later.

Show details on source website

To clipboard 

{
   affected: [
      {
         package: {
            ecosystem: "Maven",
            name: "org.apache.tika:tika-parsers",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "1.19",
                  },
                  {
                     fixed: "1.22",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
      },
   ],
   aliases: [
      "CVE-2019-10093",
   ],
   database_specific: {
      cwe_ids: [
         "CWE-770",
      ],
      github_reviewed: true,
      github_reviewed_at: "2019-08-06T01:42:09Z",
      nvd_published_at: "2019-08-02T19:15:00Z",
      severity: "MODERATE",
   },
   details: "In Apache Tika 1.19 to 1.21, a carefully crafted 2003ml or 2006ml file could consume all available SAXParsers in the pool and lead to very long hangs. Apache Tika users should upgrade to 1.22 or later.",
   id: "GHSA-4mq5-mj59-qq9c",
   modified: "2021-05-05T22:55:27Z",
   published: "2019-08-06T01:43:38Z",
   references: [
      {
         type: "ADVISORY",
         url: "https://nvd.nist.gov/vuln/detail/CVE-2019-10093",
      },
      {
         type: "WEB",
         url: "https://lists.apache.org/thread.html/39723d8227b248781898c200aa24b154683673287b150a204b83787d@%3Cdev.tika.apache.org%3E",
      },
      {
         type: "WEB",
         url: "https://lists.apache.org/thread.html/a5a44eff1b9eda3bc69d22943a1030c43d376380c75d3ab04d0c1a21@%3Cdev.tika.apache.org%3E",
      },
      {
         type: "WEB",
         url: "https://lists.apache.org/thread.html/da9ee189d1756f8508d0f2386d8e25aca5a6df541739829232be8a94@%3Cdev.tika.apache.org%3E",
      },
      {
         type: "WEB",
         url: "https://lists.apache.org/thread.html/fb6c84fd387de997e5e366d50b0ca331a328c466432c80f8c5eed33d@%3Cdev.tika.apache.org%3E",
      },
      {
         type: "WEB",
         url: "https://lists.apache.org/thread.html/r204ba2a9ea750f38d789d2bb429cc0925ad6133deea7cbc3001d96b5@%3Csolr-user.lucene.apache.org%3E",
      },
      {
         type: "WEB",
         url: "https://security.netapp.com/advisory/ntap-20190828-0004",
      },
      {
         type: "WEB",
         url: "https://www.oracle.com/security-alerts/cpuapr2020.html",
      },
      {
         type: "WEB",
         url: "https://www.oracle.com/security-alerts/cpujan2020.html",
      },
   ],
   schema_version: "1.4.0",
   severity: [
      {
         score: "CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
         type: "CVSS_V3",
      },
   ],
   summary: "Allocation of Resources Without Limits or Throttling in Apache Tika",
}


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.




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.