Hide Forgot
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 malicious example.net domain name, then example.com.example.net (as well as example.com-example.net) would be inadvertently allowed. Upstream patch: https://github.com/cyu/rack-cors/commit/42ebe6caa8e85ffa9c8a171bda668ba1acc7a5e6 References: https://github.com/cyu/rack-cors/blob/v0.4.0/lib/rack/cors.rb#L256 https://packetstormsecurity.com/files/143345/rack-cors-Missing-Anchor.html
Created rubygem-rack-cors tracking bugs for this issue: Affects: epel-all [bug 1470688] Affects: fedora-all [bug 1470689]