ID CVE-2010-1618
Summary Cross-site scripting (XSS) vulnerability in the phpCAS client library before 1.1.0, as used in Moodle 1.8.x before 1.8.12 and 1.9.x before 1.9.8, allows remote attackers to inject arbitrary web script or HTML via a crafted URL, which is not properly handled in an error message.
Vulnerable Configurations
  • cpe:2.3:a:ja-sig:phpcas_client_library:1.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:ja-sig:phpcas_client_library:1.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:moodle:moodle:1.8:*:*:*:*:*:*:*
  • cpe:2.3:a:moodle:moodle:1.8.1:*:*:*:*:*:*:*
  • cpe:2.3:a:moodle:moodle:1.8.2:*:*:*:*:*:*:*
  • cpe:2.3:a:moodle:moodle:1.8.3:*:*:*:*:*:*:*
  • cpe:2.3:a:moodle:moodle:1.8.4:*:*:*:*:*:*:*
  • cpe:2.3:a:moodle:moodle:1.8.5:*:*:*:*:*:*:*
  • cpe:2.3:a:moodle:moodle:1.8.6:*:*:*:*:*:*:*
  • cpe:2.3:a:moodle:moodle:1.8.7:*:*:*:*:*:*:*
  • cpe:2.3:a:moodle:moodle:1.8.8:*:*:*:*:*:*:*
  • cpe:2.3:a:moodle:moodle:1.8.9:*:*:*:*:*:*:*
  • cpe:2.3:a:moodle:moodle:1.8.10:*:*:*:*:*:*:*
  • cpe:2.3:a:moodle:moodle:1.8.11:*:*:*:*:*:*:*
  • cpe:2.3:a:moodle:moodle:1.9:*:*:*:*:*:*:*
  • cpe:2.3:a:moodle:moodle:1.9.1:*:*:*:*:*:*:*
  • cpe:2.3:a:moodle:moodle:1.9.2:*:*:*:*:*:*:*
  • cpe:2.3:a:moodle:moodle:1.9.3:*:*:*:*:*:*:*
  • cpe:2.3:a:moodle:moodle:1.9.4:*:*:*:*:*:*:*
  • cpe:2.3:a:moodle:moodle:1.9.5:*:*:*:*:*:*:*
  • cpe:2.3:a:moodle:moodle:1.9.6:*:*:*:*:*:*:*
  • cpe:2.3:a:moodle:moodle:1.9.7:*:*:*:*:*:*:*
Base: 4.3 (as of 22-05-2010 - 05:47)
  • Reflected XSS
    This type of attack is a form of Cross-Site Scripting (XSS) where a malicious script is "reflected" off a vulnerable web application and then executed by a victim's browser. The process starts with an adversary delivering a malicious script to a victim and convincing the victim to send the script to the vulnerable web application. The most common method of this is through a phishing email where the adversary embeds the malicious script with a URL that the victim then clicks on. In processing the subsequent request, the vulnerable web application incorrectly considers the malicious script as valid input and uses it to creates a reposnse that is then sent back to the victim. To launch a successful Reflected XSS attack, an adversary looks for places where user-input is used directly in the generation of a response. This often involves elements that are not expected to host scripts such as image tags (<img>), or the addition of event attibutes such as onload and onmouseover. These elements are often not subject to the same input validation, output encoding, and other content filtering and checking routines.
  • XSS Using MIME Type Mismatch
    An adversary creates a file with scripting content but where the specified MIME type of the file is such that scripting is not expected. The adversary tricks the victim into accessing a URL that responds with the script file. Some browsers will detect that the specified MIME type of the file does not match the actual type of its content and will automatically switch to using an interpreter for the real content type. If the browser does not invoke script filters before doing this, the adversary's script may run on the target unsanitized, possibly revealing the victim's cookies or executing arbitrary script in their browser.
  • DOM-Based XSS
    This type of attack is a form of Cross-Site Scripting (XSS) where a malicious script is inserted into the client-side HTML being parsed by a web browser. Content served by a vulnerable web application includes script code used to manipulate the Document Object Model (DOM). This script code either does not properly validate input, or does not perform proper output encoding, thus creating an opportunity for an adversary to inject a malicious script launch a XSS attack. A key distinction between other XSS attacks and DOM-based attacks is that in other XSS attacks, the malicious script runs when the vulnerable web page is initially loaded, while a DOM-based attack executes sometime after the page loads. Another distinction of DOM-based attacks is that in some cases, the malicious script is never sent to the vulnerable web server at all. An attack like this is guaranteed to bypass any server-side filtering attempts to protect users.
  • Stored XSS
    This type of attack is a form of Cross-site Scripting (XSS) where a malicious script is persistenly "stored" within the data storage of a vulnerable web application. Initially presented by an adversary to the vulnerable web application, the malicious script is incorrectly considered valid input and is not properly encoded by the web application. A victim is then convinced to use the web application in a way that creates a response that includes the malicious script. This response is subsequently sent to the victim and the malicious script is executed by the victim's browser. To launch a successful Stored XSS attack, an adversary looks for places where stored input data is used in the generation of a response. This often involves elements that are not expected to host scripts such as image tags (<img>), or the addition of event attibutes such as onload and onmouseover. These elements are often not subject to the same input validation, output encoding, and other content filtering and checking routines.
  • AJAX Fingerprinting
    This attack utilizes the frequent client-server roundtrips in Ajax conversation to scan a system. While Ajax does not open up new vulnerabilities per se, it does optimize them from an attacker point of view. In many XSS attacks the attacker must get a "hole in one" and successfully exploit the vulnerability on the victim side the first time, once the client is redirected the attacker has many chances to engage in follow on probes, but there is only one first chance. In a widely used web application this is not a major problem because 1 in a 1,000 is good enough in a widely used application. A common first step for an attacker is to footprint the environment to understand what attacks will work. Since footprinting relies on enumeration, the conversational pattern of rapid, multiple requests and responses that are typical in Ajax applications enable an attacker to look for many vulnerabilities, well-known ports, network locations and so on.
  • Cross-Site Scripting (XSS)
    An adversary embeds malicious scripts in content that will be served to web browsers. The goal of the attack is for the target software, the client-side browser, to execute the script with the users' privilege level. An attack of this type exploits a programs' vulnerabilities that are brought on by allowing remote hosts to execute code and scripts. Web browsers, for example, have some simple security controls in place, but if a remote attacker is allowed to execute scripts (through injecting them in to user-generated content like bulletin boards) then these controls may be bypassed. Further, these attacks are very difficult for an end user to detect.
cvss-vector via4 AV:N/AC:M/Au:N/C:N/I:P/A:N
refmap via4
suse SUSE-SR:2010:011
vupen ADV-2010-1107
Last major update 22-05-2010 - 05:47
Published 29-04-2010 - 21:30
Last modified 22-05-2010 - 05:47
Back to Top