Cross Site Scripting through Log Files
An attacker may leverage a system weakness where logs are susceptible to log injection to insert scripts into the system's logs. If these logs are later viewed by an administrator through a thin administrative interface and the log data is not properly HTML encoded before being written to the page, the attackers' scripts stored in the log will be executed in the administrative interface with potentially serious consequences. This attack pattern is really a combination of two other attack patterns: log injection and stored cross site scripting.
Embedding Scripts in Non-Script Elements
This attack is a form of Cross-Site Scripting (XSS) where malicious scripts are embedded in elements that are not expected to host scripts such as image tags (<img>), comments in XML documents (< !-CDATA->), etc. These tags may not be subject to the same input validation, output validation, and other content filtering and checking routines, so this can create an opportunity for an attacker to tunnel through the application's elements and launch a XSS attack through other elements.
As with all remote attacks, it is important to differentiate the ability to launch an attack (such as probing an internal network for unpatched servers) and the ability of the remote attacker to collect and interpret the output of said attack.
Embedding Scripts within Scripts
An attack of this type exploits a programs' vulnerabilities that are brought on by allowing remote hosts to execute scripts. The attacker leverages this capability to execute scripts to execute his/her own script by embedding it within other scripts that the target software is likely to execute. The attacker must have the ability to inject script into script that is likely to be executed. If this is done, then the attacker can potentially launch a variety of probes and attacks against the web server's local environment, in many cases the so-called DMZ, back end resources the web server can communicate with, and other hosts.
With the proliferation of intermediaries, such as Web App Firewalls, network devices, and even printers having JVMs and Web servers, there are many locales where an attacker can inject malicious scripts. Since this attack pattern defines scripts within scripts, there are likely privileges to execute said attack on the host.
Cross-Site Scripting in Error Pages
An attacker distributes a link (or possibly some other query structure) with a request to a third party web server that is malformed and also contains a block of exploit code in order to have the exploit become live code in the resulting error page. When the third party web server receives the crafted request and notes the error it then creates an error message that echoes the malformed message, including the exploit. Doing this converts the exploit portion of the message into to valid language elements that are executed by the viewing browser. When a victim executes the query provided by the attacker the infected error message error message is returned including the exploit code which then runs in the victim's browser. XSS can result in execution of code as well as data leakage (e.g. session cookies can be sent to the attacker). This type of attack is especially dangerous since the exploit appears to come from the third party web server, who the victim may trust and hence be more vulnerable to deception.
Cross-Site Scripting Using Alternate Syntax
The attacker uses alternate forms of keywords or commands that result in the same action as the primary form but which may not be caught by filters. For example, many keywords are processed in a case insensitive manner. If the site's web filtering algorithm does not convert all tags into a consistent case before the comparison with forbidden keywords it is possible to bypass filters (e.g., incomplete black lists) by using an alternate case structure. For example, the "script" tag using the alternate forms of "Script" or "ScRiPt" may bypass filters where "script" is the only form tested. Other variants using different syntax representations are also possible as well as using pollution meta-characters or entities that are eventually ignored by the rendering engine. The attack can result in the execution of otherwise prohibited functionality.
Cross-Site Scripting Using MIME Type Mismatch
Cross-Site Scripting in Attributes
The attacker inserts commands to perform cross-site scripting (XSS) actions in HTML attributes. Many filters do not adequately sanitize attributes against the presence of potentially dangerous commands even if they adequately sanitize tags. For example, dangerous expressions could be inserted into a style attribute in an anchor tag, resulting in the execution of malicious code when the resulting page is rendered. If a victim is tricked into viewing the rendered page the attack proceeds like a normal XSS attack, possibly resulting in the loss of sensitive cookies or other malicious activities.
Cross-Site Scripting via Encoded URI Schemes
Cross-Site Scripting Using Doubled Characters, e.g. %3C%3Cscript
The attacker bypasses input validation by using doubled characters in order to perform a cross-site scripting attack. Some filters fail to recognize dangerous sequences if they are preceded by repeated characters. For example, by doubling the < before a script command, (<<script or %3C%3script using URI encoding) the filters of some web applications may fail to recognize the presence of a script tag. If the targeted server is vulnerable to this type of bypass, the attacker can create a crafted URL or other trap to cause a victim to view a page on the targeted server where the malicious content is executed, as per a normal XSS attack.
Cross-Site Scripting Using Flash
An attacker injects malicious script to global parameters in a Flash movie via a crafted URL. The malicious script is executed in the context of the Flash movie. As such, this is a form of Cross-Site Scripting (XSS), but the abilities granted to the Flash movie make this attack more flexible.
Cross-Site Scripting with Masking through Invalid Characters in Identifiers
The attacker inserts invalid characters in identifiers to bypass application filtering of input. Filters may not scan beyond invalid characters but during later stages of processing content that follows these invalid characters may still be processed. This allows the attacker to sneak prohibited commands past filters and perform normally prohibited operations. Invalid characters may include null, carriage return, line feed or tab in an identifier. Successful bypassing of the filter can result in a XSS attack, resulting in the disclosure of web cookies or possibly other results.
Embedding Scripts in HTTP Query Strings
A variant of cross-site scripting called "reflected" cross-site scripting, the HTTP Query Strings attack consists of passing a malicious script inside an otherwise valid HTTP request query string. This is of significant concern for sites that rely on dynamic, user-generated content such as bulletin boards, news sites, blogs, and web enabled administration GUIs. The malicious script may steal session data, browse history, probe files, or otherwise execute attacks on the client side. Once the attacker has prepared the malicious HTTP query it is sent to a victim user (perhaps by email, IM, or posted on an online forum), who clicks on a normal looking link that contains a poison query string. This technique can be made more effective through the use of services like http://tinyurl.com/, which makes very small URLs that will redirect to very large, complex ones. The victim will not know what he is really clicking on.
Simple Script Injection
An attacker 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.
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.
Embedding Script (XSS) in HTTP Headers
An attack of this type exploits web applications that generate web content, such as links in a HTML page, based on unvalidated or improperly validated data submitted by other actors. XSS in HTTP Headers attacks target the HTTP headers which are hidden from most users and may not be validated by web applications.
XSS in IMG Tags
Image tags are an often overlooked, but convenient, means for a Cross Site Scripting attack. The attacker can inject script contents into an image (IMG) tag in order to steal information from a victim's browser and execute malicious scripts.
|NASL family||Windows |
|NASL id||GOOGLE_CHROME_22_0_1229_79.NASL |
|description||The version of Google Chrome installed on the remote host is earlier than 22.0.1229.79 and is, therefore, affected by the following vulnerabilities :
- Out-of-bounds write errors exist related to Skia and the PDF viewer. (CVE-2012-2874, CVE-2012-2883, CVE-2012-2895)
- Various, unspecified errors exist related to the PDF viewer. (CVE-2012-2875)
- A buffer overflow error exists related to 'SSE2' optimizations. (CVE-2012-2876)
- An unspecified error exists related to extensions and modal dialogs that can allow application crashes.
- Use-after-free errors exist related to plugin handling, 'onclick' handling, 'SVG' text references and the PDF viewer. (CVE-2012-2878, CVE-2012-2887, CVE-2012-2888, CVE-2012-2890)
- An error exists related to 'DOM' topology corruption.
- Race conditions exist in the plugin paint buffer.
- 'DOM' tree corruption can occur with plugins.
- A pointer error exists related to 'OGG' container handling. (CVE-2012-2882)
- An out-of-bounds read error exists related to Skia.
- The possibility of a double-free error exists related to application exit. (CVE-2012-2885)
- Address information can be leaked via inter process communication (IPC). (CVE-2012-2891)
- A bypass error exists related to pop-up block.
- A double-free error exists related to 'XSL' transforms.
- An error exists related to graphics context handling.
- An unspecified memory corruption issue exists in the Windows 7 kernel, as used by Google Chrome.
Successful exploitation of any of these issues could lead to an application crash or even allow arbitrary code execution, subject to the user's privileges. |
|last seen||2019-02-21 |
|plugin id||62313 |
|title||Google Chrome < 22.0.1229.79 Multiple Vulnerabilities |
|NASL family||SuSE Local Security Checks |
|NASL id||OPENSUSE-2012-721.NASL |
|description||Chromium was upgraded to version 24.0.1290 which fixed multiple security flaws. |
|last seen||2019-02-21 |
|plugin id||74788 |
|title||openSUSE Security Update : chromium (openSUSE-SU-2012:1376-1) |
|NASL family||Gentoo Local Security Checks |
|NASL id||GENTOO_GLSA-201210-07.NASL |
|description||The remote host is affected by the vulnerability described in GLSA-201210-07 (Chromium: Multiple vulnerabilities)
Multiple vulnerabilities have been discovered in Chromium. Please review the CVE identifiers and release notes referenced below for details.
A remote attacker could entice a user to open a specially crafted web site using Chromium, possibly resulting in the execution of arbitrary code with the privileges of the process, arbitrary file write, a Denial of Service condition, Cross-Site Scripting in SSL interstitial and various Universal Cross-Site Scripting attacks.
There is no known workaround at this time. |
|last seen||2019-02-21 |
|plugin id||62652 |
|title||GLSA-201210-07 : Chromium: Multiple vulnerabilities |
|NASL family||FreeBSD Local Security Checks |
|NASL id||FREEBSD_PKG_5BAE2AB4082011E2BE5F00262D5ED8EE.NASL |
|description||Google Chrome Releases reports :
 High CVE-2012-2889: UXSS in frame handling. Credit to Sergey Glazunov.
 High CVE-2012-2886: UXSS in v8 bindings. Credit to Sergey Glazunov.
 High CVE-2012-2881: DOM tree corruption with plug-ins. Credit to Chamal de Silva.
 High CVE-2012-2876: Buffer overflow in SSE2 optimizations.
Credit to Atte Kettunen of OUSPG.
 High CVE-2012-2883: Out-of-bounds write in Skia. Credit to Atte Kettunen of OUSPG.
 High CVE-2012-2887: Use-after-free in onclick handling.
Credit to Atte Kettunen of OUSPG.
 High CVE-2012-2888: Use-after-free in SVG text references.
Credit to miaubiz.
 High CVE-2012-2894: Crash in graphics context handling.
Credit to Slawomir Blazek.
 Medium CVE-2012-2877: Browser crash with extensions and modal dialogs. Credit to Nir Moshe.
 Low CVE-2012-2879: DOM topology corruption. Credit to pawlkt.
 Medium CVE-2012-2884: Out-of-bounds read in Skia. Credit to Atte Kettunen of OUSPG.
 High CVE-2012-2874: Out-of-bounds write in Skia. Credit to Google Chrome Security Team (Inferno).
                Medium CVE-2012-2875: Various lower severity issues in the PDF viewer. Credit to Mateusz Jurczyk of Google Security Team, with contributions by Gynvael Coldwind of Google Security Team.
 High CVE-2012-2878: Use-after-free in plug-in handling.
Credit to Fermin Serna of Google Security Team.
 Medium CVE-2012-2880: Race condition in plug-in paint buffer.
Credit to Google Chrome Security Team (Cris Neckar).
 High CVE-2012-2882: Wild pointer in OGG container handling.
Credit to Google Chrome Security Team (Inferno).
 Medium CVE-2012-2885: Possible double free on exit. Credit to the Chromium development community.
   High CVE-2012-2890: Use-after-free in PDF viewer. Credit to Mateusz Jurczyk of Google Security Team, with contributions by Gynvael Coldwind of Google Security Team.
 Low CVE-2012-2891: Address leak over IPC. Credit to Lei Zhang of the Chromium development community.
 Low CVE-2012-2892: Pop-up block bypass. Credit to Google Chrome Security Team (Cris Neckar).
 High CVE-2012-2893: Double free in XSL transforms. Credit to Google Chrome Security Team (Cris Neckar).
   High CVE-2012-2895: Out-of-bounds writes in PDF viewer. Credit to Mateusz Jurczyk of Google Security Team, with contributions by Gynvael Coldwind of Google Security Team. |
|last seen||2019-02-21 |
|plugin id||62340 |
|title||FreeBSD : chromium -- multiple vulnerabilities (5bae2ab4-0820-11e2-be5f-00262d5ed8ee) |