Horde Kronolith 'lib/FBView.php' Local Include File Bug Lets Remote Users Execute Arbitrary Code
SecurityTracker Alert ID: 1017316|
SecurityTracker URL: http://securitytracker.com/id/1017316
(Links to External Site)
Updated: May 22 2008|
Original Entry Date: Nov 29 2006
Execution of arbitrary code via network, User access via network|
Fix Available: Yes Vendor Confirmed: Yes Exploit Included: Yes |
Version(s): 2.0 prior to 2.0.7, 2.1 prior to 2.1.4|
A vulnerability was reported in Horde Kronolith. A remote user can include and execute arbitrary code on the target system.|
The 'Kronolith_FreeBusy_View::factory' function in 'lib/FBView.php' does not properly validate user-supplied input in the 'view' parameter. A remote user can supply a specially crafted URL to cause the target system to include and execute arbitrary PHP code from a file on the target system. The PHP code, including operating system commands, will run with the privileges of the target web service.
The vendor was notified on November 21, 2006.
A remote user can execute arbitrary PHP code and operating system commands on the target system with the privileges of the target web service.|
The vendor has issued fixed versions (2.0.7 and 2.1.4), available at:|
Vendor URL: www.horde.org/kronolith/ (Links to External Site)
Input validation error, State error|
|Underlying OS: Linux (Any), UNIX (Any)|
Source Message Contents
Subject: iDefense Security Advisory 11.29.06: Horde Kronolith Arbitrary Local|
Horde Kronolith Arbitrary Local File Inclusion Vulnerability
iDefense Security Advisory 11.27.06
Nov 27, 2006
Kronolith is a web-based calendar system written in PHP and utilizing the
Horde Application Framework. It is generally installed along side Horde's
IMP web mail product. More information can be obtained at the Kronolith
site at http://www.horde.org/kronolith/
Remote exploitation of a design error in Horde's Kronolith could allow an
authenticated web mail user to execute arbitrary PHP code under the
security context of the running Web server.
The vulnerability specifically exists due to a design error in the way it
includes certain files. Specifically, the 'lib/FBView.php' file contains a
function 'Kronolith_FreeBusy_View::factory' which will include local files
that are supplied via the 'view' HTTP GET request parameter. An excerpt
from the code follows:
177 function &factory($view)
179 $driver = basename($view);
180 require_once dirname(__FILE__) . '/FBView/' . $view . '.php';
As you can see on line 179, input validation was done. However the
resulting string was not used on line 180. Instead the unfiltered variable
coming directly from the attacker is used. By utilizing directory traversal
specifiers and null bytes, an attacker can trivially cause files stored on
the Web server to be parsed as PHP code.
Successful exploitation could allow an attacker to include an arbitrary
local file on the affected host. Due to the lack of input validation on
$GET_['view'], directory traversal specifiers could be utilized to parse
any file on the system as PHP code.
iDefense has confirmed that versions 2.0.1 through 2.1.3 of Horde Kronolith
are vulnerable to this issue. Other versions are also likely to be
iDefense is unaware of any available workarounds for this vulnerability.
VI. VENDOR RESPONSE
The Horde core team has addressed this vulnerability in versions 2.0.7 and
2.1.4 of Kronolith.
VII. CVE INFORMATION
A Mitre Corp. Common Vulnerabilities and Exposures (CVE) number has not
been assigned yet.
VIII. DISCLOSURE TIMELINE
11/21/2006 Initial vendor notification
11/21/2006 Initial vendor response
11/29/2006 Coordinated public disclosure
The discoverer of this vulnerability wishes to remain anonymous.
Get paid for vulnerability research
Free tools, research and upcoming events
X. LEGAL NOTICES
Permission is granted for the redistribution of this alert electronically.
It may not be edited in any way without the express written consent of
iDefense. If you wish to reprint the whole or any part of this alert in
any other medium other than electronically, please e-mail
firstname.lastname@example.org for permission.
Disclaimer: The information in the advisory is believed to be accurate at
the time of publishing based on currently available information. Use of
the information constitutes acceptance for use in an AS IS condition.
There are no warranties with regard to this information. Neither the
author nor the publisher accepts any liability for any direct, indirect,
or consequential loss or damage arising from use of, or reliance on, this