Unescaped Regex Vulnerability

[bzh4bzh]

json-viewer/src/renderer/data-row.js

Line 152 in 2424e90

const regex = new RegExp(searchTerm, "gi")

The RegExp constructor was called with a non-literal value. If an adversary were able to supply a malicious regex, they could cause a Regular Expression Denial of Service (ReDoS) against the application. In Node applications, this could cause the entire application to no longer be responsive to other users' requests. To remediate this issue, never allow user-supplied regular expressions. Instead, the regular expression should be hardcoded. If this is not possible, consider using an alternative regular expression engine such as node-re2. RE2 is a safe alternative that does not support backtracking, which is what leads to ReDoS. Example using re2 which does not support backtracking (Note: it is still recommended to never use user-supplied input): (Excerpt from the attached SAST Report below)

// Import the re2 module
const RE2 = require('re2');

function match(userSuppliedRegex, userInput) {
// Create a RE2 object with the user supplied regex, this is relatively safe due to RE2 not supporting backtracking which can be abused to cause long running  queries
var re = new RE2(userSuppliedRegex);
// Execute the regular expression against some userInput
var result = re.exec(userInput);
// Work with the result
}

SAST.json