Skip to content

Polynomial regular expression used on uncontrolled data in nitrado.js

High severity GitHub Reviewed Published Aug 31, 2022 to the GitHub Advisory Database • Updated Jan 29, 2023

Package

npm nitrado.js (npm)

Affected versions

< 0.2.5

Patched versions

0.2.5

Description

Impact

Possible ReDoS with lib input of {{ and with many repetitions of {{|

Patches

Patched in all versions above 0.2.5

Workarounds

No known work arounds.

References

References

Published by the National Vulnerability Database Aug 29, 2022
Published to the GitHub Advisory Database Aug 31, 2022
Reviewed Aug 31, 2022
Last updated Jan 29, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS score

0.091%
(40th percentile)

Weaknesses

CVE ID

CVE-2022-36034

GHSA ID

GHSA-vqc4-v8hc-h2jg
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.