get-func-name is a module to retrieve a functions name securely and consistently both in NodeJS and the browser. Versions prior to 2.0.1 are subject to a regular expression denial of service (redos) vulnerability which may lead to a denial of service when parsing malicious input. This vulnerability can be exploited when there is an imbalance in parentheses, which results in excessive backtracking and subsequently increases the CPU load and processing time significantly. This vulnerability can be triggered using the following input: t.repeat(54773) + t/function/i. This issue has been addressed in commit f934b228b which has been included in releases from 2.0.1. Users are advised to upgrade. There are no known workarounds for this vulnerability.
The product does not properly control the allocation and maintenance of a limited resource.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Get-func-name | Chaijs | * | 2.0.1 (excluding) |
| RHODF-4.15-RHEL-9 | RedHat | odf4/odf-console-rhel9:v4.15.0-57 | * |
| RHODF-4.16-RHEL-9 | RedHat | odf4/odf-multicluster-console-rhel9:v4.16.0-58 | * |
| Chromium-browser | Ubuntu | bionic | * |
| Chromium-browser | Ubuntu | trusty | * |
| Chromium-browser | Ubuntu | upstream | * |
| Chromium-browser | Ubuntu | xenial | * |
| Node-get-func-name | Ubuntu | bionic | * |
| Node-get-func-name | Ubuntu | focal | * |
| Node-get-func-name | Ubuntu | lunar | * |
| Node-get-func-name | Ubuntu | mantic | * |
| Node-get-func-name | Ubuntu | oracular | * |
| Node-get-func-name | Ubuntu | trusty | * |
| Node-get-func-name | Ubuntu | xenial | * |
| Qt6-webengine | Ubuntu | bionic | * |
| Qt6-webengine | Ubuntu | lunar | * |
| Qt6-webengine | Ubuntu | mantic | * |
| Qt6-webengine | Ubuntu | oracular | * |
| Qt6-webengine | Ubuntu | trusty | * |
| Qt6-webengine | Ubuntu | xenial | * |
Mitigation of resource exhaustion attacks requires that the target system either:
The first of these solutions is an issue in itself though, since it may allow attackers to prevent the use of the system by a particular valid user. If the attacker impersonates the valid user, they may be able to prevent the user from accessing the server in question.
The second solution is simply difficult to effectively institute – and even when properly done, it does not provide a full solution. It simply makes the attack require more resources on the part of the attacker.