org.webjars.npm:angular@1.4.5 vulnerabilities
-
latest version
1.8.3
-
first published
9 years ago
-
latest version published
2 years ago
-
licenses detected
- [1.0.0,)
-
package manager
Direct Vulnerabilities
Known vulnerabilities in the org.webjars.npm:angular package. This does not include vulnerabilities belonging to this package’s dependencies.
Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities and provides fixes for free.Vulnerability | Vulnerable Version |
---|---|
org.webjars.npm:angular is a WebJar for angular. Affected versions of this package are vulnerable to Improper Validation of Unsafe Equivalence in Input in the How to fix Improper Validation of Unsafe Equivalence in Input? There is no fixed version for |
[1.3.8,)
|
org.webjars.npm:angular is a WebJar for angular. Affected versions of this package are vulnerable to Incomplete Filtering of Special Elements. The Note: The How to fix Incomplete Filtering of Special Elements? There is no fixed version for |
[0,)
|
org.webjars.npm:angular is a WebJar for angular. Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS). A regular expression used to split the value of the Note: This package is EOL and will not receive any updates to address this issue. Users should migrate to @angular/core. How to fix Regular Expression Denial of Service (ReDoS)? There is no fixed version for |
[1.3.0,)
|
org.webjars.npm:angular is a WebJar for angular. Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) via the How to fix Regular Expression Denial of Service (ReDoS)? There is no fixed version for |
[1.2.23,)
|
org.webjars.npm:angular is a WebJar for angular. Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) via the How to fix Regular Expression Denial of Service (ReDoS)? There is no fixed version for |
[1.0.0,)
|
org.webjars.npm:angular is a WebJar for angular. Affected versions of this package are vulnerable to Cross-site Scripting (XSS) due to insecure page caching in the Internet Explorer browser, which allows interpolation of How to fix Cross-site Scripting (XSS)? There is no fixed version for |
[0,)
|
org.webjars.npm:angular is a WebJar for angular. Affected versions of this package are vulnerable to Cross-site Scripting (XSS). XSS may be triggered in AngularJS applications that sanitize user-controlled HTML snippets before passing them to JQLite (DOM manipulation library that's part of AngularJS) manipulates input HTML before inserting it to the DOM in One of the modifications performed expands an XHTML self-closing tag. If PoC
Note that the style element is not closed and
This will alert, as How to fix Cross-site Scripting (XSS)? Upgrade |
[,1.8.0)
|
org.webjars.npm:angular is a WebJar for angular. Affected versions of this package are vulnerable to Cross-site Scripting (XSS). The regex-based input HTML replacement may turn sanitized code into unsanitized one.
Wrapping How to fix Cross-site Scripting (XSS)? Upgrade |
[,1.8.0)
|
org.webjars.npm:angular is a WebJar for angular. Affected versions of this package are vulnerable to Denial of Service (DoS). None How to fix Denial of Service (DoS)? Upgrade |
[,1.6.3)
|
org.webjars.npm:angular is a WebJar for angular. Affected versions of this package are vulnerable to Cross-site Scripting (XSS). None How to fix Cross-site Scripting (XSS)? Upgrade |
[,1.6.5)
|
org.webjars.npm:angular is a WebJar for angular. Affected versions of this package are vulnerable to Cross-site Scripting (XSS). The How to fix Cross-site Scripting (XSS)? Upgrade |
[,1.6.0-rc.2)
|
org.webjars.npm:angular is a WebJar for angular. Affected versions of this package are vulnerable to Cross-site Scripting (XSS) through SVG files if How to fix Cross-site Scripting (XSS)? Upgrade |
[,1.6.9)
|
org.webjars.npm:angular is a WebJar for angular. Affected versions of this package are vulnerable to Cross-site Scripting (XSS).
Browsers mutate attributes values such as Here is an example of what could happen:
The sanitizer contains a bit of code that triggers this mutation on an inert piece of DOM, before angular sanitizes it. Note: Chrome 62 does not appear to mutate this particular string any more, instead it just leaves the "whitespace" in place. This probably means that Chrome 62 is no longer vulnerable to this specific attack vector. How to fix Cross-site Scripting (XSS)? Upgrade |
[,1.6.7)
|
org.webjars.npm:angular is a WebJar for angular. Affected versions of this package are vulnerable to JSONP Callback Attack. Any url could perform JSONP requests, allowing full access to the browser and the JavaScript context. This can lead to Cross-site Scripting. How to fix JSONP Callback Attack? Upgrade |
[,1.6.1)
|
org.webjars.npm:angular is a WebJar for angular. Affected versions of this package are vulnerable to Cross-site Scripting (XSS)
due to the How to fix Cross-site Scripting (XSS)? Upgrade |
[1.3.0,1.5.0-rc.2)
|
org.webjars.npm:angular is a WebJar for angular. Affected versions of this package are vulnerable to Cross-site Scripting (XSS)
via the SVG An example of a malicious SVG document would be: SVG to sanitize:
External SVG file (test.svg):
Here the SVG to sanitize loads in the How to fix Cross-site Scripting (XSS)? Upgrade |
[,1.5.0-rc.0)
|
org.webjars.npm:angular is a WebJar for angular. Affected versions of this package are vulnerable to Cross-site Scripting (XSS) attacks involving assignment on How to fix Cross-site Scripting (XSS)? Upgrade |
[,1.4.10)
|
org.webjars.npm:angular is a WebJar for angular. Affected versions of this package are vulnerable to Cross-site Scripting (XSS).
This error occurs when mXSS attack exploit browser bugs that cause some browsers parse a certain html strings into DOM, which once serialized doesn't match the original input. These browser bugs can be exploited by attackers to create payload which looks harmless to sanitizers, but due to mutations caused by the browser are turned into dangerous code once processed after sanitization. How to fix Cross-site Scripting (XSS)? Upgrade |
[,1.5.0-beta.2)
|
org.webjars.npm:angular is a WebJar for angular. Affected versions of this package are vulnerable to Clickjacking. By enabling the SVG setting without taking other precautions, you might expose your application to click-hijacking attacks. In these attacks, sanitized SVG elements could be positioned outside of the containing element and be rendered over other elements on the page (e.g. a login link). Such behavior can then result in phishing incidents. To protect against these, explicitly setup
How to fix Clickjacking? Upgrade |
[1.3.1,1.5.0-beta.0)
|
org.webjars.npm:angular is a WebJar for angular. Affected versions of this package are vulnerable to Cross-site Scripting (XSS) due to no proper sanitization of How to fix Cross-site Scripting (XSS)? Upgrade |
[1.0.0,1.5.0-beta.0)
|