Improper Neutralization of Encoded URI Schemes in a Web Page
|ID: 84||Date: (C)2012-05-14 (M)2012-11-08|
|Type: weakness||Status: DRAFT|
|Abstraction Type: Variant|
The web application improperly neutralizes user-controlled
input for executable script disguised with URI encodings.
Applicable PlatformsLanguage Class: All
Time Of Introduction
- Architecture and Design
Related Attack Patterns
|Integrity ||Unexpected state || |
| || ||Resolve all URIs to absolute or canonical representations before
processing. || || |
|Implementation || ||Carefully check each input parameter against a rigorous positive
specification (white list) defining the specific characters and format
allowed. All input should be neutralized, not just parameters that the
user is supposed to specify, but all data in the request, including tag
attributes, hidden fields, cookies, headers, the URL itself, and so
forth. A common mistake that leads to continuing XSS vulnerabilities is
to validate only fields that are expected to be redisplayed by the site.
We often encounter data from the request that is reflected by the
application server or the application that the development team did not
anticipate. Also, a field that is not currently reflected may be used by
a future developer. Therefore, validating ALL parts of the HTTP request
is recommended. || || |
|Implementation ||Output Encoding ||Use and specify an output encoding that can be handled by the
downstream component that is reading the output. Common encodings
include ISO-8859-1, UTF-7, and UTF-8. When an encoding is not specified,
a downstream component may choose a different encoding, either by
assuming a default encoding or automatically inferring which encoding is
being used, which can be erroneous. When the encodings are inconsistent,
the downstream component might treat some character or byte sequences as
special, even if they are not special in the original encoding.
Attackers might then be able to exploit this discrepancy and conduct
injection attacks; they even might be able to bypass protection
mechanisms that assume the original encoding is also being used by the
downstream component.The problem of inconsistent output encodings often arises in web
pages. If an encoding is not specified in an HTTP header, web browsers
often guess about which encoding is being used. This can open up the
browser to subtle XSS attacks. || || |
|Implementation || ||With Struts, write all data from form beans with the bean's filter
attribute set to true. || || |
|Implementation ||Identify and Reduce Attack Surface ||To help mitigate XSS attacks against the user's session cookie, set
the session cookie to be HttpOnly. In browsers that support the HttpOnly
feature (such as more recent versions of Internet Explorer and Firefox),
this attribute can prevent the user's session cookie from being
accessible to malicious client-side scripts that use document.cookie.
This is not a complete solution, since HttpOnly is not supported by all
browsers. More importantly, XMLHTTPRequest and other powerful browser
technologies provide read access to HTTP headers, including the
Set-Cookie header in which the HttpOnly flag is set. ||Defense in Depth || |
|CWE-84 ChildOf CWE-896 ||Category ||CWE-888 || |
ript:") in an IMG tag.
- CVE-2005-0692 : Encoded script within BBcode IMG tag.
For more examples, refer to CVE relations in the bottom box.
White Box Definitions None
Black Box Definitions None
|PLOVER || ||XSS using Script Via Encoded URI Schemes || |