Missing regular expression anchor¶
ID: go/regex/missing-regexp-anchor Kind: problem Security severity: 7.8 Severity: warning Precision: high Tags: - correctness - security - external/cwe/cwe-20 Query suites: - go-code-scanning.qls - go-security-extended.qls - go-security-and-quality.qls Click to see the query in the CodeQL repository
Sanitizing untrusted input with regular expressions is a common technique. However, it is error-prone to match untrusted input against regular expressions without anchors such as ^ or $. Malicious input can bypass such security checks by embedding one of the allowed patterns in an unexpected location.
Even if the matching is not done in a security-critical context, it may still cause undesirable behavior when the regular expression accidentally matches.
Recommendation¶
Use anchors to ensure that regular expressions match at the expected locations.
Example¶
The following example code checks that a URL redirection will reach the example.com domain, or one of its subdomains, and not some malicious site.
packagemainimport("errors""net/http""regexp")funccheckRedirect2(req*http.Request,via[]*http.Request)error{// BAD: the host of `req.URL` may be controlled by an attackerre:="https?://www\\.example\\.com/"ifmatched,_:=regexp.MatchString(re,req.URL.String());matched{returnnil}returnerrors.New("Invalid redirect")}The check with the regular expression match is, however, easy to bypass. For example, the string http://example.com/ can be embedded in the query string component: http://evil-example.net/?x=http://example.com/.
Address these shortcomings by using anchors in the regular expression instead:
packagemainimport("errors""net/http""regexp")funccheckRedirect2Good(req*http.Request,via[]*http.Request)error{// GOOD: the host of `req.URL` cannot be controlled by an attackerre:="^https?://www\\.example\\.com/"ifmatched,_:=regexp.MatchString(re,req.URL.String());matched{returnnil}returnerrors.New("Invalid redirect")}A related mistake is to write a regular expression with multiple alternatives, but to only anchor one of the alternatives. As an example, the regular expression ^www\.example\.com|beta\.example\.com will match the host evil.beta.example.com because the regular expression is parsed as (^www\.example\.com)|(beta\.example\.com)/, so the second alternative beta\.example\.com is not anchored at the beginning of the string.
When checking for a domain name that may have subdomains, it is important to anchor the regular expression or ensure that the domain name is prefixed with a dot.
packagemainimport("regexp")funccheckSubdomain(domainString){// Checking strictly that the domain is `example.com`.re:="^example\\.com$"ifmatched,_:=regexp.MatchString(re,domain);matched{// domain is good.}// GOOD: Alternatively, check the domain is `example.com` or a subdomain of `example.com`.re2:="(^|\\.)example\\.com$"ifmatched,_:=regexp.MatchString(re2,domain);matched{// domain is good.}}