CWE-83Improper Neutralization of Script in Attributes in a Web Page

Description

Common consequences· 1

• Confidentiality / Integrity / Availability — Read Application Data, Execute Unauthorized Code or Commands

Potential mitigations· 4

• [Implementation]Carefully check each input parameter against a rigorous positive specification (allowlist) 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]
• [Implementation]With Struts, write all data from form beans with the bean's filter attribute set to true.
• [Implementation]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.

Related CAPEC attack patterns· 3

Exploits (incoming)3

(incoming)1

Related by meaning· 6

Nearest entities by semantic similarity across the cs-graph corpus.