Bug 840318 - ganglia: Arbitrary PHP files may be executed from the Ganglia server due to unsanitized input to graph.php
Summary: ganglia: Arbitrary PHP files may be executed from the Ganglia server due to u...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: ganglia
Version: el6
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Kostas Georgiou
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 840316
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-07-15 20:05 UTC by Kostas Georgiou
Modified: 2012-07-31 17:02 UTC (History)
3 users (show)

Fixed In Version:
Clone Of: 840316
Environment:
Last Closed: 2012-07-31 17:02:23 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Kostas Georgiou 2012-07-15 20:05:45 UTC 
+++ This bug was initially created as a clone of Bug #840316 +++

Was reported upstream at http://bugzilla.ganglia.info/cgi-bin/bugzilla/show_bug.cgi?id=333
Comment 1 Fedora Update System 2012-07-15 20:12:06 UTC 
ganglia-3.1.7-6.el6 has been submitted as an update for Fedora EPEL 6.
https://admin.fedoraproject.org/updates/ganglia-3.1.7-6.el6
Comment 2 Tomas Hoger 2012-07-16 08:52:17 UTC 
Does EPEL-5 version (3.0.7-1.el5) need this fix?
Comment 3 Kostas Georgiou 2012-07-16 11:07:11 UTC 
No the code seems safe there
Comment 4 Fedora Update System 2012-07-16 17:01:16 UTC 
Package ganglia-3.1.7-6.el6:
* should fix your issue,
* was pushed to the Fedora EPEL 6 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=epel-testing ganglia-3.1.7-6.el6'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-EPEL-2012-6408/ganglia-3.1.7-6.el6
then log in and leave karma (feedback).
Comment 5 Fedora Update System 2012-07-31 17:02:23 UTC 
ganglia-3.1.7-6.el6 has been pushed to the Fedora EPEL 6 stable repository.  If problems still persist, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.