NodeJS/angular/1.5.5


HTML enhanced for web apps

https://www.npmjs.com/package/angular
MIT

13 Security Vulnerabilities

Cross-Site Scripting via JSONP

Published date: 2019-06-27T17:25:42Z
Links:

JSONP allows untrusted resource URLs, which provides a vector for attack by malicious actors.

Affected versions: ["1.6.0-rc.2", "1.6.0-rc.1", "1.6.0-rc.0", "1.5.11", "1.5.10", "1.5.9", "1.5.8", "1.5.7", "1.5.6", "1.5.5", "1.5.3", "1.5.2", "1.5.1", "1.5.0", "1.5.0-rc.2", "1.5.0-rc.1", "1.5.0-rc.0", "1.5.0-beta.2", "1.5.0-beta.0", "1.4.14", "1.4.13", "1.4.12", "1.4.11", "1.4.10", "1.4.9", "1.4.8", "1.4.7", "1.4.6", "1.4.5", "1.4.4", "1.4.3", "1.4.2", "1.4.1", "1.4.0", "1.4.0-rc.2", "1.4.0-rc.1", "1.4.0-rc.0", "1.4.0-beta.6", "1.4.0-beta.5", "1.4.0-beta.4", "1.4.0-beta.3", "1.4.0-beta.2", "1.4.0-beta.1", "1.4.0-beta.0", "1.3.20", "1.3.19", "1.3.18", "1.3.17", "1.3.16", "1.3.15", "1.3.14", "1.3.13", "1.3.12", "1.3.11", "1.3.10", "1.3.9", "1.3.8", "1.3.7", "1.3.6", "1.3.5", "1.3.4", "1.3.4-build.3588", "1.3.3", "1.3.2", "1.3.1", "1.3.0", "1.3.0-rc.5", "1.2.32", "1.2.31", "1.2.30", "1.2.29", "1.2.28", "1.2.27", "1.2.23", "1.2.22", "1.2.21", "1.2.20", "1.2.19", "1.2.18", "1.2.17", "1.2.16", "1.2.15", "1.2.14", "1.2.13", "1.2.12", "1.2.11", "1.2.10", "1.2.9", "1.2.8", "1.2.7", "1.2.6", "1.2.5", "1.2.4", "1.2.3", "1.2.2", "1.2.1", "1.2.0", "1.1.5", "1.1.4", "1.1.3", "1.1.2", "1.1.1", "1.1.0", "1.0.8", "1.0.7", "1.0.6", "1.0.5", "1.0.4", "1.0.3", "1.0.2", "1.0.1", "1.0.0", "0.0.4", "0.0.3", "0.0.2", "0.0.1", "0.0.1-2", "0.0.1-1"]
Secure versions: []

angular vulnerable to regular expression denial of service via the $resource service

Published date: 2023-03-30T06:30:26Z
CVE: CVE-2023-26117
Links:

All versions of the package angular are vulnerable to Regular Expression Denial of Service (ReDoS) via the $resource service due to the usage of an insecure regular expression. Exploiting this vulnerability is possible by a large carefully-crafted input, which can result in catastrophic backtracking.

Affected versions: ["1.8.3", "1.8.2", "1.8.1", "1.8.0", "1.7.9", "1.7.8", "1.7.7", "1.7.6", "1.7.5", "1.7.4", "1.7.3", "1.7.2", "1.7.1", "1.7.0", "1.7.0-rc.0", "1.6.10", "1.6.9", "1.6.8", "1.6.7", "1.6.6", "1.6.5", "1.6.4", "1.6.3", "1.6.2", "1.6.1", "1.6.0", "1.6.0-rc.2", "1.6.0-rc.1", "1.6.0-rc.0", "1.5.11", "1.5.10", "1.5.9", "1.5.8", "1.5.7", "1.5.6", "1.5.5", "1.5.3", "1.5.2", "1.5.1", "1.5.0", "1.5.0-rc.2", "1.5.0-rc.1", "1.5.0-rc.0", "1.5.0-beta.2", "1.5.0-beta.0", "1.4.14", "1.4.13", "1.4.12", "1.4.11", "1.4.10", "1.4.9", "1.4.8", "1.4.7", "1.4.6", "1.4.5", "1.4.4", "1.4.3", "1.4.2", "1.4.1", "1.4.0", "1.4.0-rc.2", "1.4.0-rc.1", "1.4.0-rc.0", "1.4.0-beta.6", "1.4.0-beta.5", "1.4.0-beta.4", "1.4.0-beta.3", "1.4.0-beta.2", "1.4.0-beta.1", "1.4.0-beta.0", "1.3.20", "1.3.19", "1.3.18", "1.3.17", "1.3.16", "1.3.15", "1.3.14", "1.3.13", "1.3.12", "1.3.11", "1.3.10", "1.3.9", "1.3.8", "1.3.7", "1.3.6", "1.3.5", "1.3.4", "1.3.4-build.3588", "1.3.3", "1.3.2", "1.3.1", "1.3.0", "1.3.0-rc.5", "1.2.32", "1.2.31", "1.2.30", "1.2.29", "1.2.28", "1.2.27", "1.2.23", "1.2.22", "1.2.21", "1.2.20", "1.2.19", "1.2.18", "1.2.17", "1.2.16", "1.2.15", "1.2.14", "1.2.13", "1.2.12", "1.2.11", "1.2.10", "1.2.9", "1.2.8", "1.2.7", "1.2.6", "1.2.5", "1.2.4", "1.2.3", "1.2.2", "1.2.1", "1.2.0", "1.1.5", "1.1.4", "1.1.3", "1.1.2", "1.1.1", "1.1.0", "1.0.8", "1.0.7", "1.0.6", "1.0.5", "1.0.4", "1.0.3", "1.0.2", "1.0.1", "1.0.0", "0.0.4", "0.0.3", "0.0.2", "0.0.1", "0.0.1-2", "0.0.1-1"]
Secure versions: []

angular vulnerable to regular expression denial of service via the angular.copy() utility

Published date: 2023-03-30T06:30:26Z
CVE: CVE-2023-26116
Links:

All versions of the package angular are vulnerable to Regular Expression Denial of Service (ReDoS) via the angular.copy() utility function due to the usage of an insecure regular expression. Exploiting this vulnerability is possible by a large carefully-crafted input, which can result in catastrophic backtracking.

Affected versions: ["1.8.3", "1.8.2", "1.8.1", "1.8.0", "1.7.9", "1.7.8", "1.7.7", "1.7.6", "1.7.5", "1.7.4", "1.7.3", "1.7.2", "1.7.1", "1.7.0", "1.7.0-rc.0", "1.6.10", "1.6.9", "1.6.8", "1.6.7", "1.6.6", "1.6.5", "1.6.4", "1.6.3", "1.6.2", "1.6.1", "1.6.0", "1.6.0-rc.2", "1.6.0-rc.1", "1.6.0-rc.0", "1.5.11", "1.5.10", "1.5.9", "1.5.8", "1.5.7", "1.5.6", "1.5.5", "1.5.3", "1.5.2", "1.5.1", "1.5.0", "1.5.0-rc.2", "1.5.0-rc.1", "1.5.0-rc.0", "1.5.0-beta.2", "1.5.0-beta.0", "1.4.14", "1.4.13", "1.4.12", "1.4.11", "1.4.10", "1.4.9", "1.4.8", "1.4.7", "1.4.6", "1.4.5", "1.4.4", "1.4.3", "1.4.2", "1.4.1", "1.4.0", "1.4.0-rc.2", "1.4.0-rc.1", "1.4.0-rc.0", "1.4.0-beta.6", "1.4.0-beta.5", "1.4.0-beta.4", "1.4.0-beta.3", "1.4.0-beta.2", "1.4.0-beta.1", "1.4.0-beta.0", "1.3.20", "1.3.19", "1.3.18", "1.3.17", "1.3.16", "1.3.15", "1.3.14", "1.3.13", "1.3.12", "1.3.11", "1.3.10", "1.3.9", "1.3.8", "1.3.7", "1.3.6", "1.3.5", "1.3.4", "1.3.4-build.3588", "1.3.3", "1.3.2", "1.3.1", "1.3.0", "1.3.0-rc.5", "1.2.32", "1.2.31", "1.2.30", "1.2.29", "1.2.28", "1.2.27", "1.2.23", "1.2.22", "1.2.21", "1.2.20", "1.2.19", "1.2.18", "1.2.17", "1.2.16", "1.2.15", "1.2.14", "1.2.13", "1.2.12", "1.2.11", "1.2.10", "1.2.9", "1.2.8", "1.2.7", "1.2.6", "1.2.5", "1.2.4", "1.2.3", "1.2.2", "1.2.1", "1.2.0", "1.1.5", "1.1.4", "1.1.3", "1.1.2", "1.1.1", "1.1.0", "1.0.8", "1.0.7", "1.0.6", "1.0.5", "1.0.4", "1.0.3", "1.0.2", "1.0.1", "1.0.0", "0.0.4", "0.0.3", "0.0.2", "0.0.1", "0.0.1-2", "0.0.1-1"]
Secure versions: []

angular vulnerable to super-linear runtime due to backtracking

Published date: 2024-02-10T06:30:19Z
CVE: CVE-2024-21490
Links:

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

Note:

This package is EOL and will not receive any updates to address this issue. Users should migrate to @angular/core.

Affected versions: ["1.8.3", "1.8.2", "1.8.1", "1.8.0", "1.7.9", "1.7.8", "1.7.7", "1.7.6", "1.7.5", "1.7.4", "1.7.3", "1.7.2", "1.7.1", "1.7.0", "1.7.0-rc.0", "1.6.10", "1.6.9", "1.6.8", "1.6.7", "1.6.6", "1.6.5", "1.6.4", "1.6.3", "1.6.2", "1.6.1", "1.6.0", "1.6.0-rc.2", "1.6.0-rc.1", "1.6.0-rc.0", "1.5.11", "1.5.10", "1.5.9", "1.5.8", "1.5.7", "1.5.6", "1.5.5", "1.5.3", "1.5.2", "1.5.1", "1.5.0", "1.5.0-rc.2", "1.5.0-rc.1", "1.5.0-rc.0", "1.5.0-beta.2", "1.5.0-beta.0", "1.4.14", "1.4.13", "1.4.12", "1.4.11", "1.4.10", "1.4.9", "1.4.8", "1.4.7", "1.4.6", "1.4.5", "1.4.4", "1.4.3", "1.4.2", "1.4.1", "1.4.0", "1.4.0-rc.2", "1.4.0-rc.1", "1.4.0-rc.0", "1.4.0-beta.6", "1.4.0-beta.5", "1.4.0-beta.4", "1.4.0-beta.3", "1.4.0-beta.2", "1.4.0-beta.1", "1.4.0-beta.0", "1.3.20", "1.3.19", "1.3.18", "1.3.17", "1.3.16", "1.3.15", "1.3.14", "1.3.13", "1.3.12", "1.3.11", "1.3.10", "1.3.9", "1.3.8", "1.3.7", "1.3.6", "1.3.5", "1.3.4", "1.3.4-build.3588", "1.3.3", "1.3.2", "1.3.1", "1.3.0"]
Secure versions: []

XSS via JQLite DOM manipulation functions in AngularJS

Published date: 2020-08-05T21:47:02Z
Links:

Summary

XSS may be triggered in AngularJS applications that sanitize user-controlled HTML snippets before passing them to JQLite methods like JQLite.prepend, JQLite.after, JQLite.append, JQLite.replaceWith, JQLite.append, new JQLite and angular.element.

Description

JQLite (DOM manipulation library that's part of AngularJS) manipulates input HTML before inserting it to the DOM in jqLiteBuildFragment.

One of the modifications performed expands an XHTML self-closing tag.

If jqLiteBuildFragment is called (e.g. via new JQLite(aString)) with user-controlled HTML string that was sanitized (e.g. with DOMPurify), the transformation done by JQLite may modify some forms of an inert, sanitized payload into a payload containing JavaScript - and trigger an XSS when the payload is inserted into DOM.

This is similar to a bug in jQuery htmlPrefilter function that was fixed in 3.5.0.

Proof of concept

const inertPayload = `<div><style><style/><img src=x onerror="alert(1337)"/>` 

Note that the style element is not closed and <img would be a text node inside the style if inserted into the DOM as-is. As such, some HTML sanitizers would leave the <img as is without processing it and stripping the onerror attribute.

angular.element(document).append(inertPayload);

This will alert, as <style/> will be replaced with <style></style> before adding it to the DOM, closing the style element early and reactivating img.

Patches

The issue is patched in JQLite bundled with angular 1.8.0. AngularJS users using JQuery should upgrade JQuery to 3.5.0, as a similar vulnerability affects jQuery <3.5.0.

Workarounds

Changing sanitizer configuration not to allow certain tag grouping (e.g. <option><style></option>) or inline style elements may stop certain exploitation vectors, but it's uncertain if all possible exploitation vectors would be covered. Upgrade of AngularJS to 1.8.0 is recommended.

References

https://github.com/advisories/GHSA-mhp6-pxh8-r675 https://github.com/jquery/jquery/security/advisories/GHSA-gxr4-xjj5-5px2 https://github.com/jquery/jquery/security/advisories/GHSA-jpcq-cgw6-v4j6 https://blog.jquery.com/2020/04/10/jquery-3-5-0-released/ https://snyk.io/vuln/SNYK-JS-ANGULAR-570058

Affected versions: ["1.7.9", "1.7.8", "1.7.7", "1.7.6", "1.7.5", "1.7.4", "1.7.3", "1.7.2", "1.7.1", "1.7.0", "1.7.0-rc.0", "1.6.10", "1.6.9", "1.6.8", "1.6.7", "1.6.6", "1.6.5", "1.6.4", "1.6.3", "1.6.2", "1.6.1", "1.6.0", "1.6.0-rc.2", "1.6.0-rc.1", "1.6.0-rc.0", "1.5.11", "1.5.10", "1.5.9", "1.5.8", "1.5.7", "1.5.6", "1.5.5", "1.5.3", "1.5.2", "1.5.1", "1.5.0", "1.5.0-rc.2", "1.5.0-rc.1", "1.5.0-rc.0", "1.5.0-beta.2", "1.5.0-beta.0", "1.4.14", "1.4.13", "1.4.12", "1.4.11", "1.4.10", "1.4.9", "1.4.8", "1.4.7", "1.4.6", "1.4.5", "1.4.4", "1.4.3", "1.4.2", "1.4.1", "1.4.0", "1.4.0-rc.2", "1.4.0-rc.1", "1.4.0-rc.0", "1.4.0-beta.6", "1.4.0-beta.5", "1.4.0-beta.4", "1.4.0-beta.3", "1.4.0-beta.2", "1.4.0-beta.1", "1.4.0-beta.0", "1.3.20", "1.3.19", "1.3.18", "1.3.17", "1.3.16", "1.3.15", "1.3.14", "1.3.13", "1.3.12", "1.3.11", "1.3.10", "1.3.9", "1.3.8", "1.3.7", "1.3.6", "1.3.5", "1.3.4", "1.3.4-build.3588", "1.3.3", "1.3.2", "1.3.1", "1.3.0", "1.3.0-rc.5", "1.2.32", "1.2.31", "1.2.30", "1.2.29", "1.2.28", "1.2.27", "1.2.23", "1.2.22", "1.2.21", "1.2.20", "1.2.19", "1.2.18", "1.2.17", "1.2.16", "1.2.15", "1.2.14", "1.2.13", "1.2.12", "1.2.11", "1.2.10", "1.2.9", "1.2.8", "1.2.7", "1.2.6", "1.2.5", "1.2.4", "1.2.3", "1.2.2", "1.2.1", "1.2.0", "1.1.5", "1.1.4", "1.1.3", "1.1.2", "1.1.1", "1.1.0", "1.0.8", "1.0.7", "1.0.6", "1.0.5", "1.0.4", "1.0.3", "1.0.2", "1.0.1", "1.0.0", "0.0.4", "0.0.3", "0.0.2", "0.0.1", "0.0.1-2", "0.0.1-1"]
Secure versions: []

Angular's deprecated package has a Cross-Site Scripting issue

Published date: 2026-06-24T21:30:44Z
CVE: CVE-2026-11998
Links:

A flaw in AngularJS' Strict Contextual Escaping (SCE) logic allows bypassing certain SCE policies for resource URLs and can lead to arbitrary JavaScript execution within the context of the victim's browser session.

SCE's purpose is to ensure that only trusted or safe values are used in certain security-sensitive contexts, such as resource URLs, including URLs that define executable JavaScript scripts, '