CVE-2010-3077: XSS

Published Sep 6, 2010
·
Updated

Cross-site scripting (XSS) vulnerability in util/iconbrowser.php in the Horde Application Framework before 3.3.9 allows remote attackers to inject arbitrary web script or HTML via the subdir parameter.

Other sources

Moritz Naumann reported: [1] http://seclists.org/fulldisclosure/2010/Sep/82

a deficiency in the way Horde framework sanitized user-provided 'subdir' parameter, when composing final path to the image file. A remote, unauthenticated user could use this flaw to conduct cross-site scripting attacks (execute arbitrary HTML or scripting code) by providing a specially-crafted URL to the running Horde framework instance.

Upstream patch: [2] http://git.horde.org/diff.php/horde/util/iconbrowser.php?rt=horde-git&r1=a978a35c3e95e784253508fd4333d2fbb64830b6&r2=9342addbd2b95f184f230773daa4faf5ef6d65e9

Sample public URL by Moritz to demonstrate the issue: [3] [pathtohorde]/util/iconbrowser.php?subdir=<body onload="alert('XSS')">&app=horde

Affected Software

84 affected components
Horde Horde Application Framework=3.0.11
Horde Horde Application Framework=2.0-rc3
Horde Horde Application Framework=3.2.3
Horde Horde Application Framework=2.0
Horde Horde Application Framework=3.0-rc3
Horde Horde Application Framework=3.3.4-rc1
Horde Horde Application Framework=3.2
Horde Horde Application Framework=3.1.4-rc1
Horde Horde Application Framework=2.2.5
Horde Horde Application Framework=3.1
Horde Horde Application Framework=3.0-rc1
Horde Horde Application Framework=3.0.4
Horde Horde Application Framework=3.0.6-rc1
Horde Horde Application Framework=3.1.9
Horde Horde Application Framework=3.1-rc2
Horde Horde Application Framework=3.0
Horde Horde Application Framework=3.1.8
Horde Horde Application Framework=3.1.2
Horde Horde Application Framework=2.2.9
Horde Horde Application Framework=2.2.3
Horde Horde Application Framework=2.0-rc1
Horde Horde Application Framework=3.2-alpha
Horde Horde Application Framework=1.3.3
Horde Horde Application Framework=3.0.5
Horde Horde Application Framework=1.3.1
Horde Horde Application Framework=3.0.10
Horde Horde Application Framework=3.0.1
Horde Horde Application Framework=3.0-rc2
Horde Horde Application Framework=3.3.7
Horde Horde Application Framework=3.0.4-rc1
Horde Horde Application Framework=2.2.8
Horde Horde Application Framework=3.1-rc1
Horde Horde Application Framework=2.2.6
Horde Horde Application Framework=3.3
Horde Horde Application Framework=3.2-rc4
Horde Horde Application Framework=3.1.1
Horde Horde Application Framework=3.0.8
Horde Horde Application Framework=1.3.2
Horde Horde Application Framework=3.1.7
Horde Horde Application Framework=3.1.5
Horde Horde Application Framework=3.3.2
Horde Horde Application Framework=2.2.7
Horde Horde Application Framework=3.0.3
Horde Horde Application Framework=3.2-rc1
Horde Horde Application Framework=3.3-rc1
Horde Horde Application Framework=3.0.6
Horde Horde Application Framework=3.2-rc3
Horde Horde Application Framework=3.1-rc3
Horde Horde Application Framework=3.0.4-rc2
Horde Horde Application Framework=2.2.6-rc1
Horde Horde Application Framework=1.3.0
Horde Horde Application Framework<=3.3.8
Horde Horde Application Framework=3.0.5-rc2
Horde Horde Application Framework=2.2
Horde Horde Application Framework=3.3.4
Horde Horde Application Framework=3.0-alpha
Horde Horde Application Framework=1.3.5
Horde Horde Application Framework=2.2.1
Horde Horde Application Framework=3.3.5
Horde Horde Application Framework=3.2.1
Horde Horde Application Framework=2.2.2
Horde Horde Application Framework=3.2.5
Horde Horde Application Framework=3.3.1
Horde Horde Application Framework=3.2.2
Horde Horde Application Framework=3.0-beta
Horde Horde Application Framework=3.0.9
Horde Horde Application Framework=3.3.6
Horde Horde Application Framework=1.3.4
Horde Horde Application Framework=3.0.12
Horde Horde Application Framework=3.1.3
Horde Horde Application Framework=3.1.6
Horde Horde Application Framework=2.2.4
Horde Horde Application Framework=1.1.1
Horde Horde Application Framework=3.2.4
Horde Horde Application Framework=3.0.7
Horde Horde Application Framework=3.0.5-rc1
Horde Horde Application Framework=2.0-rc4
Horde Horde Application Framework=3.1.4
Horde Horde Application Framework=3.3.3
Horde Horde Application Framework=3.2-rc2
Horde Horde Application Framework=2.1
Horde Horde Application Framework=3.0.2
Horde Horde Application Framework=3.0.3-rc1
Horde Horde Application Framework=1.0.3

Event History

Sep 6, 2010
Data Sourced
06:06 PM
DescriptionSeverityAffected Software
Nov 9, 2010
CVE Published
via MITRE·08:00 PM
Data Sourced
via MITRE·08:00 PM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2010-3077?

CVE-2010-3077 is classified as a medium severity cross-site scripting (XSS) vulnerability.

2

How do I fix CVE-2010-3077?

To fix CVE-2010-3077, upgrade the Horde Application Framework to version 3.3.9 or later.

3

Which versions of the Horde Application Framework are affected by CVE-2010-3077?

CVE-2010-3077 affects all Horde Application Framework versions prior to 3.3.9 and certain earlier versions.

4

What type of vulnerability is CVE-2010-3077?

CVE-2010-3077 is a cross-site scripting (XSS) vulnerability that allows attackers to inject arbitrary web scripts.

5

Can I still use versions before 3.3.9 with CVE-2010-3077?

Using versions before 3.3.9 while CVE-2010-3077 is unpatched poses a security risk.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203