Bug 1230765 - CVE-2015-4165 elasticsearch: unspecified arbitrary files modification vulnerability [fedora-all]
Summary: CVE-2015-4165 elasticsearch: unspecified arbitrary files modification vulnera...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: elasticsearch
Version: 22
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: jiri vanek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: fst_owner=dcafaro, fst_ping=1
Depends On:
Blocks: CVE-2015-4165
TreeView+ depends on / blocked
 
Reported: 2015-06-11 13:47 UTC by Vasyl Kaigorodov
Modified: 2015-08-11 01:55 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Release Note
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-08-11 01:55:22 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Vasyl Kaigorodov 2015-06-11 13:47:54 UTC
This is an automatically created tracking bug!  It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of Fedora.

For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.

For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs

When submitting as an update, use the fedpkg template provided in the next
comment(s).  This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.

Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.

NOTE: this issue affects multiple supported versions of Fedora. While only
one tracking bug has been filed, please correct all affected versions at
the same time.  If you need to fix the versions independent of each other,
you may clone this bug as appropriate.

[bug automatically created by: add-tracking-bugs]

Comment 1 Vasyl Kaigorodov 2015-06-11 13:48:00 UTC
Use the following template to for the 'fedpkg update' request to submit an
update for this issue as it contains the top-level parent bug(s) as well as
this tracking bug.  This will ensure that all associated bugs get updated
when new packages are pushed to stable.

=====

# bugfix, security, enhancement, newpackage (required)
type=security

# testing, stable
request=testing

# Bug numbers: 1234,9876
bugs=1230761,1230765

# Description of your update
notes=Security fix for CVE-2015-4165

# Enable request automation based on the stable/unstable karma thresholds
autokarma=True
stable_karma=3
unstable_karma=-3

# Automatically close bugs when this marked as stable
close_bugs=True

# Suggest that users restart after update
suggest_reboot=False

======

Additionally, you may opt to use the bodhi update submission link instead:

https://admin.fedoraproject.org/updates/new/?type_=security&bugs=1230761,1230765

Comment 2 jiri vanek 2015-06-12 08:19:33 UTC
Hello, this is about:
https://www.elastic.co/blog/elasticsearch-1-6-0-released#fs-config

Or any other vulnereability?

Comment 3 jiri vanek 2015-06-12 09:41:30 UTC
If so, then here is build for rawhide:
http://koji.fedoraproject.org/koji/taskinfo?taskID=10029367
and here update for f22. Let me know if th eupdate should change from enhancement to security.
https://admin.fedoraproject.org/updates/elasticsearch-1.6.0-0.fc22

Comment 4 David A. Cafaro 2015-07-23 01:39:41 UTC
Noticed another issue came up regarding elasticsearch in this ticket:

https://bugzilla.redhat.com/show_bug.cgi?id=1244239

Maybe update and roll a patch out for both at this point?

I believe these should be classified as security not enhancement at this point as well.

Comment 5 David A. Cafaro 2015-08-05 13:54:49 UTC
Still need a patch for this, any update?

Comment 6 jiri vanek 2015-08-10 12:31:11 UTC
Not sure what is wonted from me. ES 1.6.1 published in bodhi
https://admin.fedoraproject.org/updates/FEDORA-2015-12031/elasticsearch-1.6.1-0.fc22 as security update  immediately after  1.6.1 (and 1.7.1  for rawhide) was available.  According to karma nobody cared.

I have not added any bugs because   non of the specified bugs is actually describing vulnerability.

If this bugs are describing  the vulnerabilities for which 1.{6,7}.1 was release, please close those bugs. Otherwise please give me reproducer, contat ES usptream or fix it and I will add you to comaintainers.

Comment 7 David A. Cafaro 2015-08-11 01:55:22 UTC
Looks like this somehow missed getting tagged with the 1.6.1 release (which fixes this issue).

Thanks for pointing that out.


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