Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
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
CVE-2018-1335 tika: Command injection in tika-server can allow remote attacke...
Status: NEW
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
high Severity high
: ---
: ---
Assigned To: Red Hat Product Security
impact=important,public=20180425,repo...
: Security
Depends On: 1614537 1572417 1572418
Blocks: 1572420
  Show dependency treegraph
 
Reported: 2018-04-26 21:16 EDT by Sam Fowler
Modified: 2018-08-14 18:51 EDT (History)
41 users (show)

See Also:
Fixed In Version: tika 1.18
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Sam Fowler 2018-04-26 21:16:39 EDT
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:

https://lists.apache.org/thread.html/b3ed4432380af767effd4c6f27665cc7b2686acccbefeb9f55851dca@%3Cdev.tika.apache.org%3E
Comment 1 Sam Fowler 2018-04-26 21:17:26 EDT
Created tika tracking bugs for this issue:

Affects: fedora-all [bug 1572418]
Comment 6 Andrej Nemec 2018-05-14 11:53:11 EDT
Statement:

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/.

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