Subresource Integrity (SRI) Not Used Template

Executive Summary:

This report addresses a significant security vulnerability regarding the absence of Subresource Integrity (SRI) within our application. SRI Not Used occurs when external resources are included without cryptographic integrity checks, leaving the application vulnerable to attacks such as code injection, data manipulation, or supply chain attacks. This report aims to detail the vulnerability, its potential impact, and recommendations for mitigation.

Description of the Vulnerability:

SRI Not Used vulnerabilities arise when external resources, such as JavaScript or CSS files, are included in the application without implementing Subresource Integrity checks. SRI provides a security mechanism to ensure that the fetched resource has not been tampered with during transmission. Without SRI, attackers can potentially inject malicious code into external resources, compromise user security, or manipulate the behavior of the application.


The impact of SRI Not Used vulnerabilities can be severe, leading to security risks such as code injection, data theft, or compromise of user privacy. Attackers can exploit these vulnerabilities to inject malicious scripts into external resources, manipulate user interactions, or exfiltrate sensitive information, potentially resulting in financial loss, reputational damage, or legal consequences for our organization.


The likelihood of exploitation depends on various factors, including the visibility and accessibility of external resources within our application, the security measures implemented to validate the integrity of these resources, and the attacker's knowledge and motivation. However, given the prevalence of supply chain attacks and the potential impact on application security and user privacy, the risk associated with SRI Not Used is significant if not properly mitigated.

Steps to Reproduce:

  1. Identify external resources, such as JavaScript or CSS files, included within our application.
  2. Analyze the inclusion of these external resources to determine if Subresource Integrity (SRI) checks are implemented.
  3. Attempt to inject malicious code or modify the content of external resources.
  4. Determine if attackers can exploit SRI Not Used vulnerabilities to inject malicious scripts, compromise user security, or manipulate the behavior of the application.

Recommendations for Developers:

  1. Implement Subresource Integrity (SRI): Ensure that external resources are included using SRI attributes to verify their integrity and prevent tampering.
  2. Regularly Monitor External Dependencies: Monitor and update external dependencies to mitigate the risk of supply chain attacks and ensure the integrity of included resources.


Addressing SRI Not Used vulnerabilities is critical to protecting against code injection, data manipulation, and supply chain attacks within our application. By implementing Subresource Integrity (SRI) checks and regularly monitoring external dependencies, we can mitigate the risks associated with SRI Not Used and enhance the overall security posture of our systems.