George Kalpakas

A flaw in the Strict Contextual Escaping (SCE) logic allows the bypass of policies for resource URLs, which can lead to arbitrary JavaScript execution in the victim's browser session. SCE is designed to ensure only trusted values are used in security-sensitive contexts, such as URLs for executable scripts, `<iframe>` documents, and route templates. The issue occurs because the logic used to match entire URLs against regular expression matchers can result in partial matches for certain regular expressions, allowing unsafe values to be used as resource URLs.

The ECDSA implementation within the Elliptic package produces incorrect signatures when an interim value of `k` (calculated according to step 3.2 of RFC 6979) contains leading zeros, making it susceptible to cryptanalysis and potentially exposing the secret key. This occurs because the byte-length of `k` is calculated incorrectly, leading to truncation during computation. This can disrupt legitimate transactions or communications. An attacker, under specific conditions, could derive the secret key by obtaining both a faulty signature generated by a vulnerable version of Elliptic and a correct signature for the same inputs.

Name of the Vulnerable Software and Affected Versions: AngularJS (affected versions not specified) Description: A regular expression used by the AngularJS linky filter to detect URLs in input text is vulnerable to super-linear runtime due to backtracking, potentially leading to a Regular expression Denial of Service (ReDoS) attack. The AngularJS project is End-of-Life and will not receive updates to address this issue. Recommendations: At the moment, there is no information about a newer version that contains a fix for this vulnerability.

The issue is related to improper sanitization of the `href` and `xlink:href` attributes in `<image>` SVG elements in the `ngSanitize` module. This allows attackers to bypass common image source restrictions, potentially leading to Content Spoofing and negatively affecting the application's performance and behavior by using large or slow-to-load images.

The issue is related to improper sanitization of the `href` and `xlink:href` attributes in `<image>` SVG elements, allowing attackers to bypass common image source restrictions. This can lead to Content Spoofing and negatively affect the application's performance and behavior by using too large or slow-to-load images.

Name of the Vulnerable Software and Affected Versions: AngularJS versions all Description: The issue is related to improper sanitization of the value of the `[srcset]` attribute in `<source>` HTML elements in AngularJS, allowing attackers to bypass common image source restrictions. This can also lead to a form of Content Spoofing. The AngularJS project is End-of-Life and will not receive any updates to address this issue. Recommendations: At the moment, there is no information about a newer version that contains a fix for this vulnerability.

Name of the Vulnerable Software and Affected Versions: AngularJS versions 1.3.0-rc.4 and greater Description: The issue is due to improper sanitization of the value of the `[srcset]` attribute in AngularJS, allowing attackers to bypass common image source restrictions. This can lead to a form of Content Spoofing. The AngularJS project is End-of-Life and will not receive any updates to address this issue. Recommendations: At the moment, there is no information about a newer version that contains a fix for this vulnerability.

A regular expression used to split the value of the `ng-srcset` directive is vulnerable to super-linear runtime due to backtracking. With large carefully-crafted input, this can result in catastrophic backtracking and cause a denial of service.

The issue is related to the angular.copy() utility function, which uses an insecure regular expression. This can lead to a Regular Expression Denial of Service (ReDoS) via a large carefully-crafted input, resulting in catastrophic backtracking. Exploiting this issue is possible, allowing a remote attacker to cause a denial of service.

The issue is related to the $resource service in angular, which uses an insecure regular expression. This can lead to a Regular Expression Denial of Service (ReDoS) when a large, carefully-crafted input is provided, resulting in catastrophic backtracking. The vulnerability can be exploited by a remote attacker to cause a denial of service.

The issue is related to the usage of an insecure regular expression in the input[url] functionality of the angular package, which can lead to a Regular Expression Denial of Service (ReDoS) via the <input type="url"> element. Exploiting this vulnerability is possible by a large carefully-crafted input, which can result in catastrophic backtracking. This can allow a remote attacker to cause a denial of service.