Bug 1572416 (CVE-2018-1335) - CVE-2018-1335 tika: Command injection in tika-server can allow remote attackers to execute arbitrary commands via crafted headers
Summary: CVE-2018-1335 tika: Command injection in tika-server can allow remote attacke...
Alias: CVE-2018-1335
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On: 1572417 1572418 1614537
Blocks: 1572420
TreeView+ depends on / blocked
Reported: 2018-04-27 01:16 UTC by Sam Fowler
Modified: 2021-02-17 00:24 UTC (History)
37 users (show)

Fixed In Version: tika 1.18
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-10-17 18:51:24 UTC

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2019:3140 0 None None None 2019-10-17 14:54:51 UTC

Description Sam Fowler 2018-04-27 01:16:39 UTC
Apache Tika before version 1.18 has a command injection vulnerability in tika-server. A remote attacker could exploit this to execute arbitrary commands via crafted headers.

External References:


Comment 1 Sam Fowler 2018-04-27 01:17:26 UTC
Created tika tracking bugs for this issue:

Affects: fedora-all [bug 1572418]

Comment 6 Andrej Nemec 2018-05-14 15:53:11 UTC

This issue affects the versions of tika which is embedded in the nutch package  as shipped with Red Hat Satellite 5. The tika server is not exposed, as such exploitation is difficult, Red Hat Product Security has rated this issue as having security impact of Low. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.

Comment 11 errata-xmlrpc 2019-10-17 14:54:48 UTC
This issue has been addressed in the following products:

  Red Hat JBoss Data Virtualization 6.4.8

Via RHSA-2019:3140 https://access.redhat.com/errata/RHSA-2019:3140

Comment 12 Product Security DevOps Team 2019-10-17 18:51:24 UTC
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):


Note You need to log in before you can comment on or make changes to this bug.