QID 356305

jquery before 1.9.0 is vulnerable to cross-site scripting (xss) attacks.
The jquery(strinput) function does not differentiate selectors from html in a reliable fashion.
In vulnerable versions, jquery determined whether the input was html by looking for the < character anywhere in the string, giving attackers more flexibility when attempting to construct a malicious payload.
In fixed versions, jquery only deems the input to be html if it explicitly starts with the < character, limiting exploitability only to attackers who can control the beginning of a string, which is far less common. (
( CVE-2012-6708) jquery before 3.0.0 is vulnerable to cross-site scripting (xss) attacks when a cross-domain ajax request is performed without the datatype option, causing text/javascript responses to be executed. (
( CVE-2015-9251) a flaw was discovered in ruby in the way certain functions handled strings containing null bytes.
Specifically, the built-in methods file.fnmatch and its alias file.fnmatch?
Did not properly handle path patterns containing the null byte.
A remote attacker could exploit this flaw to make a ruby script access unexpected files and to bypass intended file system access restrictions. (
( CVE-2019-15845) webrick::httpauth::digestauth in ruby through 2.4.7, 2.5.x through 2.5.6, and 2.6.x through 2.6.4 has a regular expression denial of service cause by looping/backtracking.
A victim must expose a webrick server that uses digestauth to the internet or a untrusted network. (
( CVE-2019-16201) ruby through 2.4.7, 2.5.x through 2.5.6, and 2.6.x through 2.6.4 allows http response splitting.
An attacker can exploit this to call an arbitrary ruby method. (

Note: The preceding description block is extracted directly from the security advisory. Using automation, we have attempted to clean and format it as much as possible without introducing additional issues.

Successful exploitation of this vulnerability could lead to a securitybreach or could affect integrity, availability, and confidentiality.