Missing Regex anchor in Rack-Cors allows malicious third party site to perform CORS request
High severity
GitHub Reviewed
Published
Jul 31, 2018
to the GitHub Advisory Database
•
Updated Sep 5, 2023
Description
Published to the GitHub Advisory Database
Jul 31, 2018
Reviewed
Jun 16, 2020
Last updated
Sep 5, 2023
Missing anchor in generated regex for rack-cors before 0.4.1 allows a malicious third-party site to perform CORS requests. If the configuration were intended to allow only the trusted
example.com
domain name and not the maliciousexample.net
domain name, thenexample.com.example.net
(as well asexample.com-example.net
) would be inadvertently allowed.References