The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special characters such as " ", and "&" that could be interpreted as web-scripting elements when they are sent to a downstream component that processes web pages.

What CVEs are caused by CWE-80?

479 recorded CVEs are attributed to CWE-80, including CVE-2020-13965, CVE-2023-39216, CVE-2024-34070. 1 are listed in CISA's Known Exploited Vulnerabilities (KEV) catalog.

How is CWE-80 detected?

Automated Static Analysis: Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)

What are the consequences of CWE-80?

Exploiting CWE-80 can lead to: Read Application Data, Execute Unauthorized Code or Commands.

Is CWE-80 actively exploited?

Yes. 1 CWE-80 vulnerabilities are in CISA's KEV catalog of actively exploited flaws, out of 479 recorded CVEs.

CWE-80: Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS)

How to prevent it

Practical mitigations for CWE-80, grouped by where in the lifecycle they apply.

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 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

Attack Surface Reduction

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.

Effectiveness: Defense in Depth

Frequently asked questions

Common questions about CWE-80.

What is CWE-80?: The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special characters such as " ", and "&" that could be interpreted as web-scripting elements when they are sent to a downstream component that processes web pages.
What CVEs are caused by CWE-80?: 479 recorded CVEs are attributed to CWE-80, including CVE-2020-13965, CVE-2023-39216, CVE-2024-34070. 1 are listed in CISA's Known Exploited Vulnerabilities (KEV) catalog.
How do you prevent CWE-80?: 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 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.
How is CWE-80 detected?: Automated Static Analysis: Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)
What are the consequences of CWE-80?: Exploiting CWE-80 can lead to: Read Application Data, Execute Unauthorized Code or Commands.
Is CWE-80 actively exploited?: Yes. 1 CWE-80 vulnerabilities are in CISA's KEV catalog of actively exploited flaws, out of 479 recorded CVEs.

CWE-80: Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS)

Overview

Real-world CVEs

Common consequences

How it happens

When it is introduced

Applies to

How to prevent it

How to detect it

Automated Static Analysis

Code examples

Illustrative examples

Terminology & mappings

Mapped taxonomies

Attack patterns

Frequently asked questions

References

Stay ahead of CWE-80

Overview

Real-world CVEs

Common consequences

How it happens

When it is introduced

Applies to

How to prevent it

How to detect it

Automated Static Analysis

Code examples

Illustrative examples

Related weaknesses

Parent

Terminology & mappings

Mapped taxonomies

Attack patterns

Frequently asked questions

References

Stay ahead of CWE-80