The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers). An example of a network attack is an attacker causing a denial of service by sending a specially crafted TCP packet across a wide area network (e.g., CVE-2004-0230).
Attack Complexity
Low
AC
The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Privileges Required
None
PR
The attacker is unauthenticated prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
Scope
Unchanged
S
An exploited vulnerability can only affect resources managed by the same security authority. In the case of a vulnerability in a virtualized environment, an exploited vulnerability in one guest instance would not affect neighboring guest instances.
Confidentiality
Low
C
There is some impact on confidentiality, but the attacker either does not gain control of any data, or the information obtained does not have a significant impact on the system or its operations.
Integrity
Low
I
Modification of data is possible, but the attacker does not have control over what can be modified, or the extent of what the attacker can affect is limited. The data modified does not have a direct, serious impact on the system.
Availability
Low
A
There is reduced performance or interruptions in resource availability. However, the attacker does not have the ability to completely prevent access to the resources or services; the impact is limited.
Author: Stan Bubrouski
Date: December 16, 2005
Package: WebCal (by Michael Arndt; http://bulldog.tzo.org/webcal/webcal.html)
Versions Affected: 1.11-3.04 (unknown <1.11)
Severity: XSS allowing cookie theft, etc..
Description:
This particular WebCal (there are in fact over a dozen separate webcal
projects), suffers from cross-site scripting (XSS) vulnerabilities
using almost any parameters sent to any of the included CGI (perl)
scripts. Here are a couple examples using version 3.04:
http://bulldog.tzo.org/perl/webcal.cgi?function=<script>alert(document.c
ookie)</script>&cal=public
http://bulldog.tzo.org/perl/webcal.cgi?function=webyear&cal=public&year=
<script>alert(document.cookie)</script>
http://bulldog.tzo.org/perl/webcal.cgi?function=webday&cal=public&date=<
script>alert(document.cookie)</script>
These examples however are just the tip of the iceburg, there are many
many more. For example you can put full scripts in new calendar
entries, as notes for entries, etc... there is no input validation.
Googling for this particular WebCal shows thousands of sites still run
it, and most of them are schools and colleges in the USA. What is
scarier is that people are running this calendar on their main sites,
where they host webmail and other session-cookie based webapps.
Solution:
WebCal development ceased in early 2003, meaning nobody is going to be
updating it in all likelyhood. While it may be possible to patch all
the XSS holes, a better alternative would be to find a newer,
supported calendar program. There are plenty of perl, PHP, and JSP
alternatives that should be considered.
This information is provided for TESTING and LEGAL RESEARCH purposes only. All trademarks used are properties of their respective owners. By visiting this website you agree to Terms of Use and Privacy Policy and Impressum