Related Weaknesses
CWE-ID |
Weakness Name |
Source |
CWE-79 |
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
|
Metrics
Metrics |
Score |
Severity |
CVSS Vector |
Source |
V2 |
4.3 |
|
AV:N/AC:M/Au:N/C:N/I:P/A:N |
nvd@nist.gov |
EPSS
EPSS is a scoring model that predicts the likelihood of a vulnerability being exploited.
EPSS Score
The EPSS model produces a probability score between 0 and 1 (0 and 100%). The higher the score, the greater the probability that a vulnerability will be exploited.
EPSS Percentile
The percentile is used to rank CVE according to their EPSS score. For example, a CVE in the 95th percentile according to its EPSS score is more likely to be exploited than 95% of other CVE. Thus, the percentile is used to compare the EPSS score of a CVE with that of other CVE.
Exploit information
Exploit Database EDB-ID : 33407
Publication date : 2009-12-14 23h00 +00:00
Author : Juan Galiana Lara
EDB Verified : Yes
source: https://www.securityfocus.com/bid/37351/info
Horde Framework is prone to a cross-site scripting vulnerability because it fails to sufficiently sanitize user-supplied data.
An attacker may leverage this issue to execute arbitrary script code in the browser of an unsuspecting user in the context of the affected site. This may help the attacker steal cookie-based authentication credentials and launch other attacks.
This issue affects versions prior to Horde 3.3.6.
Note that additional products that use the Horde framework may also be vulnerable.
http://www.example.com/horde-3.3.5/admin/cmdshell.php/%22%3E%3Cscript%3Ealert%288%29;%3C/script%3E%3Cform%20/?Horde=<sessid>
Exploit Database EDB-ID : 33408
Publication date : 2009-12-14 23h00 +00:00
Author : Juan Galiana Lara
EDB Verified : Yes
source: https://www.securityfocus.com/bid/37351/info
Horde Framework is prone to a cross-site scripting vulnerability because it fails to sufficiently sanitize user-supplied data.
An attacker may leverage this issue to execute arbitrary script code in the browser of an unsuspecting user in the context of the affected site. This may help the attacker steal cookie-based authentication credentials and launch other attacks.
This issue affects versions prior to Horde 3.3.6.
Note that additional products that use the Horde framework may also be vulnerable.
http://www.example.com/horde-3.3.5/admin/sqlshell.php/%22%3E%3Cscript%3Ealert%288%29;%3C/script%3E%3Cform%20/?Horde=<sessid>
Exploit Database EDB-ID : 10512
Publication date : 2009-12-16 23h00 +00:00
Author : Juan Galiana Lara
EDB Verified : Yes
=============================================
INTERNET SECURITY AUDITORS ALERT 2009-012
- Original release date: October 13th, 2009
- Last revised: December 16th, 2009
- Discovered by: Juan Galiana Lara
- CVE ID: CVE-2009-3701
- Severity: 6.3/10 (CVSS Base Score)
=============================================
I. VULNERABILITY
-------------------------
Horde 3.3.5 "PHP_SELF" Cross-Site Scripting vulnerability
II. BACKGROUND
-------------------------
The Horde Application Framework is a modular, general-purpose web
application framework written in PHP. It provides an extensive array
of classes that are targeted at the common problems and tasks involved
in developing modern web applications.
III. DESCRIPTION
-------------------------
Input passed to 'PHP_SELF' variable is not properly filtered before
being returned to the user. This can be explotied to inject arbitrary
HTML or to execute arbitrary script code in a user's browser session
in context of an affected site. In order to successfully exploit this
vulnerability the targeted user has to be logged as an administrator.
horde-3.3.5/admin/cmdshell.php:46:<form action="<?php echo
$_SERVER['PHP_SELF'] ?>" method="post">
horde-3.3.5/admin/sqlshell.php:29:<form name="sqlshell" action="<?php
echo $_SERVER['PHP_SELF'] ?>" method="post">
horde-3.3.5/admin/phpshell.php:42:<form action="<?php echo
$_SERVER['PHP_SELF'] ?>" method="post">
In order to filter the "PHP_SELF" variable, the htmlspecialchars
function has to be used, like in
'horde-3.3.5/templates/shares/edit.inc' file:
horde-3.3.5/templates/shares/edit.inc:1:<form name="edit"
method="post" action="<?php echo
htmlspecialchars($_SERVER['PHP_SELF']) ?>">
IV. PROOF OF CONCEPT
-------------------------
This PoC will show an alert with the text "8"
http://site/horde-3.3.5/admin/phpshell.php/%22%3E%3Cscript%3Ealert%288%29;%3C/script%3E%3Cform%20/?Horde=<sessid>
http://site/horde-3.3.5/admin/cmdshell.php/%22%3E%3Cscript%3Ealert%288%29;%3C/script%3E%3Cform%20/?Horde=<sessid>
http://site/horde-3.3.5/admin/sqlshell.php/%22%3E%3Cscript%3Ealert%288%29;%3C/script%3E%3Cform%20/?Horde=<sessid>
V. BUSINESS IMPACT
-------------------------
Is possible to execute arbitrary HTML or script code in a targeted
user's browser. Only works with administration sessions.
VI. SYSTEMS AFFECTED
-------------------------
Horde 3.3.5 is vulnerable, others may be affected.
VII. SOLUTION
-------------------------
Upgrade to version 3.3.6
VIII. REFERENCES
-------------------------
http://www.horde.org
http://lists.horde.org/archives/announce/2009/000529.html
http://www.isecauditors.com
IX. CREDITS
-------------------------
This vulnerability has been discovered by
Juan Galiana Lara (jgaliana (at) isecauditors (dot) com).
X. REVISION HISTORY
-------------------------
October 13, 2009: Initial release
October 19, 2009: Added CVE id.
December 13, 2009: Revision.
December 16, 2009: Las revision.
XI. DISCLOSURE TIMELINE
-------------------------
October 13, 2009: Vulnerability discovered by
Internet Security Auditors.
October 13, 2009: Sent to developers.
The issue is considered hard to exploit and
solution is delayed.
December 13, 2009: Second contact for correction plan.
December 15, 2009: New release published.
December 16, 2009: Sent to public lists.
XII. LEGAL NOTICES
-------------------------
The information contained within this advisory is supplied "as-is"
with no warranties or guarantees of fitness of use or otherwise.
Internet Security Auditors accepts no responsibility for any damage
caused by the use or misuse of this information.
Exploit Database EDB-ID : 33406
Publication date : 2009-12-14 23h00 +00:00
Author : Juan Galiana Lara
EDB Verified : Yes
source: https://www.securityfocus.com/bid/37351/info
Horde Framework is prone to a cross-site scripting vulnerability because it fails to sufficiently sanitize user-supplied data.
An attacker may leverage this issue to execute arbitrary script code in the browser of an unsuspecting user in the context of the affected site. This may help the attacker steal cookie-based authentication credentials and launch other attacks.
This issue affects versions prior to Horde 3.3.6.
Note that additional products that use the Horde framework may also be vulnerable.
http://www.example.com/horde-3.3.5/admin/phpshell.php/%22%3E%3Cscript%3Ealert%288%29;%3C/script%3E%3Cform%20/?Horde=<sessid>
Products Mentioned
Configuraton 0
Horde>>Application_framework >> Version To (including) 3.3.5
Horde>>Application_framework >> Version 2.0
Horde>>Application_framework >> Version 2.1
Horde>>Application_framework >> Version 2.1.3
Horde>>Application_framework >> Version 2.2
Horde>>Application_framework >> Version 2.2.1
Horde>>Application_framework >> Version 2.2.3
Horde>>Application_framework >> Version 2.2.4
Horde>>Application_framework >> Version 2.2.4_rc1
Horde>>Application_framework >> Version 2.2.5
Horde>>Application_framework >> Version 2.2.6
Horde>>Application_framework >> Version 3.0
Horde>>Application_framework >> Version 3.0.1
Horde>>Application_framework >> Version 3.0.2
Horde>>Application_framework >> Version 3.0.3
Horde>>Application_framework >> Version 3.0.4
Horde>>Application_framework >> Version 3.0.6
Horde>>Application_framework >> Version 3.0.7
Horde>>Application_framework >> Version 3.0.8
Horde>>Application_framework >> Version 3.0.9
Horde>>Application_framework >> Version 3.1
Horde>>Application_framework >> Version 3.1.1
Horde>>Application_framework >> Version 3.2
Horde>>Application_framework >> Version 3.2.1
Horde>>Application_framework >> Version 3.2.2
Horde>>Application_framework >> Version 3.2.3
Horde>>Application_framework >> Version 3.2.4
Horde>>Application_framework >> Version 3.3
Horde>>Application_framework >> Version 3.3.1
Horde>>Application_framework >> Version 3.3.2
Horde>>Application_framework >> Version 3.3.3
Horde>>Application_framework >> Version 3.3.4
Horde>>Groupware >> Version To (including) 1.2.4
Horde>>Groupware >> Version 1.0
Horde>>Groupware >> Version 1.0.1
Horde>>Groupware >> Version 1.0.2
Horde>>Groupware >> Version 1.0.3
Horde>>Groupware >> Version 1.0.4
Horde>>Groupware >> Version 1.0.5
Horde>>Groupware >> Version 1.1
Horde>>Groupware >> Version 1.1.1
Horde>>Groupware >> Version 1.1.2
Horde>>Groupware >> Version 1.1.3
Horde>>Groupware >> Version 1.1.4
Horde>>Groupware >> Version 1.1.5
Horde>>Groupware >> Version 1.2
Horde>>Groupware >> Version 1.2
Horde>>Groupware >> Version 1.2.1
Horde>>Groupware >> Version 1.2.2
Horde>>Groupware >> Version 1.2.3
Configuraton 0
Horde>>Groupware >> Version To (including) 1.2.4
Horde>>Groupware >> Version 1.0
Horde>>Groupware >> Version 1.0
Horde>>Groupware >> Version 1.0
Horde>>Groupware >> Version 1.0.1
Horde>>Groupware >> Version 1.0.2
Horde>>Groupware >> Version 1.0.3
Horde>>Groupware >> Version 1.0.4
Horde>>Groupware >> Version 1.0.5
Horde>>Groupware >> Version 1.0.6
Horde>>Groupware >> Version 1.0.7
Horde>>Groupware >> Version 1.0.8
Horde>>Groupware >> Version 1.1
Horde>>Groupware >> Version 1.1
Horde>>Groupware >> Version 1.1
Horde>>Groupware >> Version 1.1
Horde>>Groupware >> Version 1.1
Horde>>Groupware >> Version 1.1.1
Horde>>Groupware >> Version 1.1.2
Horde>>Groupware >> Version 1.1.3
Horde>>Groupware >> Version 1.1.4
Horde>>Groupware >> Version 1.1.5
Horde>>Groupware >> Version 1.1.6
Horde>>Groupware >> Version 1.2
Horde>>Groupware >> Version 1.2
Horde>>Groupware >> Version 1.2.1
Horde>>Groupware >> Version 1.2.2
Horde>>Groupware >> Version 1.2.3
Horde>>Groupware >> Version 1.2.3
References