Angular Sanitize, a crucial module for AngularJS applications focused on securing HTML, saw a minor version increment from 1.5.5 to 1.5.6 in May 2016. Both versions serve the same core purpose: sanitizing HTML to prevent cross-site scripting (XSS) attacks by removing potentially malicious code snippets. For developers using AngularJS, this module is essential for displaying user-generated content or handling HTML from external sources safely. The license remains consistent at MIT.
The key difference between the 1.5.5 and 1.5.6 versions, while not immediately apparent from the metadata, likely involves bug fixes, performance improvements, or minor security enhancements within the sanitization logic. Developers upgrading from version 1.5.5 to 1.5.6 should anticipate improved stability and potentially better performance in how HTML is processed. To understand the specific modifications, consulting the detailed changelog on the AngularJS GitHub repository is highly recommended, as the provided data offers only a high-level overview.
By upgrading to the newer version, developers can be sure to have the latest version of Angular Sanitize. Both have been published by the Angular Core Team and are available as tarballs.
Developers should prioritize staying updated with the most recent minor versions to benefit from cumulative fixes and enhancements within the AngularJS ecosystem.
All the vulnerabilities related to the version 1.5.6 of the package
AngularJS Incomplete Filtering of Special Elements vulnerability
Improper sanitization of the value of the 'href' and 'xlink:href' attributes in '<image>' SVG elements in AngularJS's 'ngSanitize' module allows attackers to bypass common image source restrictions. This can lead to a form of Content Spoofing https://owasp.org/www-community/attacks/Content_Spoofing and also negatively affect the application's performance and behavior by using too large or slow-to-load images.
This issue affects AngularJS versions greater than or equal to 1.3.1.
Note: The AngularJS project is End-of-Life and will not receive any updates to address this issue. For more information see here https://docs.angularjs.org/misc/version-support-status .