You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The original Identity Server 4 code base has several medium impact security bugs detected by CodeQL scanning.
Description:
Extracting text from a DOM node and interpreting it as HTML can lead to a cross-site scripting vulnerability.
A webpage with this vulnerability reads text from the DOM, and afterwards adds the text as HTML to the DOM. Using text from the DOM as HTML effectively unescapes the text, and thereby invalidates any escaping done on the text. If an attacker is able to control the safe sanitized text, then this vulnerability can be exploited to perform a cross-site scripting attack.
To guard against cross-site scripting, consider using contextual output encoding/escaping before writing text to the page, or one of the other solutions that are mentioned in the References section below.
Example
The following example shows a webpage using a data-target attribute to select and manipulate a DOM element using the JQuery library. In the example, the data-target attribute is read into the target variable, and the $ function is then supposed to use the target variable as a CSS selector to determine which element should be manipulated.
However, if an attacker can control the data-target attribute, then the value of target can be used to cause the $ function to execute arbitrary JavaScript.
The above vulnerability can be fixed by using $.find instead of $. The $.find function will only interpret target as a CSS selector and never as HTML, thereby preventing an XSS attack.
DOM text reinterpreted as HTML
The original Identity Server 4 code base has several medium impact security bugs detected by CodeQL scanning.
Description:
Extracting text from a DOM node and interpreting it as HTML can lead to a cross-site scripting vulnerability.
A webpage with this vulnerability reads text from the DOM, and afterwards adds the text as HTML to the DOM. Using text from the DOM as HTML effectively unescapes the text, and thereby invalidates any escaping done on the text. If an attacker is able to control the safe sanitized text, then this vulnerability can be exploited to perform a cross-site scripting attack.
Examples
Issues:
Recommendation
To guard against cross-site scripting, consider using contextual output encoding/escaping before writing text to the page, or one of the other solutions that are mentioned in the References section below.
Example
The following example shows a webpage using a
data-target
attribute to select and manipulate a DOM element using the JQuery library. In the example, thedata-target
attribute is read into thetarget
variable, and the$
function is then supposed to use thetarget
variable as a CSS selector to determine which element should be manipulated.However, if an attacker can control the
data-target
attribute, then the value oftarget
can be used to cause the$
function to execute arbitrary JavaScript.The above vulnerability can be fixed by using
$.find
instead of$
. The$.find
function will only interprettarget
as a CSS selector and never as HTML, thereby preventing an XSS attack.References
The text was updated successfully, but these errors were encountered: