{"answers":{"affected":"2 open source packages ship an affected version, including org.apache.tika:tika-parsers. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-10093 in the wild and no public exploit code.","fix":"Upgrade org.apache.tika:tika-parsers to 1.22 or later.","what":"CVE-2019-10093 is a medium-severity denial of service vulnerability in Apache Tika, published on 2 Aug 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2019-10093 and fix it if it is affected.\n\nWhat it is: CVE-2019-10093 is a medium-severity denial of service vulnerability in Apache Tika, published on 2 Aug 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2019-10093 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.apache.tika:tika-parsers (Maven): affected from 1.19; fixed in 1.22\n- org.apache.tika:tika-parsers (Maven): affected from 1.19; fixed in 1.22\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2019-10093/ (Markdown: https://insights.sbomify.com/CVE-2019-10093/index.md)","id":"CVE-2019-10093","markdown":"https://insights.sbomify.com/CVE-2019-10093/index.md","name":"CVE-2019-10093","record":{"aliases":["DEBIAN-CVE-2019-10093","GHSA-4mq5-mj59-qq9c"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Java content extraction library","requires_auth":"none","summary":"Attackers can cause application hangs by submitting crafted files that exhaust SAXParser pools in Apache Tika.","user_interaction":"required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"tika","vendor":"apache"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H","version":"3.0"},"cwes":[{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"}],"description":"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.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Allocation of Resources Without Limits or Throttling in Apache Tika","id":"CVE-2019-10093","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"denial_of_service","year":"2019"},"n_packages":2,"n_references":8,"next":{"headline":"Allocation of Resources Without Limits or Throttling in Apache Tika","id":"CVE-2019-10094"},"packages":[{"ecosystem":"Maven","fixed":["1.22"],"introduced":["1.19"],"last_affected":[],"package":"org.apache.tika:tika-parsers","purl":null,"source":"GHSA-4mq5-mj59-qq9c"},{"ecosystem":"Maven","fixed":["1.22"],"introduced":["1.19"],"last_affected":[],"package":"org.apache.tika:tika-parsers","purl":"pkg:maven/org.apache.tika/tika-parsers","source":"GHSA-4mq5-mj59-qq9c"}],"prev":{"headline":"Cross-site scripting in Apache HTTP Server","id":"CVE-2019-10092"},"products":["Apache Tika"],"published":"2019-08-02","related":[{"cvss_score":8.8,"headline":"Allocation of Resources Without Limits or Throttling in Apache Tika","id":"CVE-2019-10088","kev_date_added":null,"published":"2019-08-02"},{"cvss_score":8.4,"headline":"Apache Tika has XXE vulnerability","id":"CVE-2025-66516","kev_date_added":null,"published":"2025-12-04"},{"cvss_score":8.4,"headline":"Apache Tika PDF parser module: XXE vulnerability in PDFParser's handling of XFA","id":"CVE-2025-54988","kev_date_added":null,"published":"2025-08-20"},{"cvss_score":8.1,"headline":"Command injection in org.apache.tika:tika-core","id":"CVE-2018-1335","kev_date_added":null,"published":"2018-04-25"},{"cvss_score":7.8,"headline":"Allocation of Resources Without Limits or Throttling in Apache Tika","id":"CVE-2019-10094","kev_date_added":null,"published":"2019-08-02"},{"cvss_score":7.8,"headline":"Apache Tika does not properly initialize the XML parser or choose handlers","id":"CVE-2016-4434","kev_date_added":null,"published":"2017-09-29"},{"cvss_score":7.5,"headline":"Apache Tika is vulnerable to entity expansions which can lead to a denial of service attack","id":"CVE-2018-11796","kev_date_added":null,"published":"2018-10-09"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["Apache"]},"summary":"Attackers can cause application hangs by submitting crafted files that exhaust SAXParser pools in Apache Tika.","url":"https://insights.sbomify.com/CVE-2019-10093/"}