CVE-2023-26117: Regular Expression Denial of Service in angular

angular Updated 02 Oct 2025

Summary

30/03/2023
No i
Moderate
5.3

CVE-2023-26117: angular vulnerable to regular expression denial of service via the $resource service. Affects angular versions < 1.8.3. No fix is published. How to fix ↓

Also tracked for

The same CVE-2023-26117 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

Angular is an open-source JavaScript framework developed by Google. It is widely used for building web applications and provides a comprehensive set of features for creating dynamic and responsive user interfaces. The $resource service in Angular allows developers to interact with RESTful APIs. However, all versions of the package angular are vulnerable to Regular Expression Denial of Service (ReDoS) due to the usage of an insecure regular expression.

Vulnerability Detail

The vulnerability in Angular arises from the insecure regular expression used in the $resource service. An attacker can exploit this vulnerability by providing a large, carefully-crafted input that triggers catastrophic backtracking. This can lead to a denial of service (DoS) attack, where the application becomes unresponsive or crashes. The impact of this vulnerability can be severe, as it can affect the availability and performance of the application.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

If upgrading to a fixed version is not immediately feasible, developers can implement input validation and sanitization to mitigate the risk of a ReDoS attack. By carefully validating and limiting the size of user input, the likelihood of triggering catastrophic backtracking can be reduced. Here is an example of input validation using a regular expression in JavaScript:

const input = getUserInput();
const regex = /^[a-zA-Z0-9]+$/;

if (regex.test(input)) {
  // Proceed with processing the input
} else {
  // Reject the input
}

Conclusion

In conclusion, the angular package is vulnerable to Regular Expression Denial of Service (ReDoS) via the $resource service. It is crucial to update to a fixed version or implement input validation and sanitization to mitigate the risk. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for angular →

Share this vulnerability

FAQ

Angular is an open-source JavaScript framework developed by Google for building web applications. It provides a comprehensive set of features for creating dynamic and responsive user interfaces.

The $resource service in Angular allows developers to interact with RESTful APIs. It provides a high-level interface for performing CRUD operations on server resources.

Regular Expression Denial of Service (ReDoS) is a type of vulnerability that arises when a regular expression is susceptible to catastrophic backtracking. This can be exploited by an attacker to cause a denial of service (DoS) attack.

This vulnerability can lead to a denial of service (DoS) attack, where the application becomes unresponsive or crashes. It can affect the availability and performance of the application.

To mitigate the risk of a ReDoS attack, it is recommended to implement input validation and sanitization. By carefully validating and limiting the size of user input, the likelihood of triggering catastrophic backtracking can be reduced.

Related vulnerabilities

Recent vulnerabilities recorded for angular.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback