Weakness (CWE)
CWE-777: Regular Expression without Anchors
The product uses a regular expression to perform neutralization, but the regular expression omits one or more anchors that may allow malicious or malformed data to slip through.
How to prevent it (1 mitigation)
-
Implementation
Be sure to understand both what will be matched and what will not be matched by a regular expression. Anchoring the ends of the expression will allow the programmer to define an allowlist strictly limited to what is matched by the text in the regular expression. If you are using a package that only matches one line by default, ensure that you can match multi-line inputs if necessary.
Source: MITRE CWE-777
4 results · Clear filters · Feed
-
Medium 5.4
tinyauth before 5.1.3 allows rule bypass by appending an allowed route string. This is caused by an unanchored regular …
-
Medium 5.3
Webmin information disclosure via regex pattern
Webmin allows unauthenticated attackers to read the contents of any file ending in .conf within module directories, due to a bypassable regex pattern.
-
Medium 6.4
ntfy.sh allows a remote attacker to execute arbitrary code via the parseActions function
ntfy before 2.22.0 allows SSRF because of an unanchored regular expression for web push endpoint URLs.
-
Medium 5.3
Showdownjs Denial of Service
An issue in the anchors subparser of Showdownjs versions <= 2.1.0 could allow a remote attacker to cause denial of service conditions.