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.
References
Link | Resource |
---|---|
https://packetstormsecurity.com/files/143345/rack-cors-Missing-Anchor.html | Third Party Advisory VDB Entry |
https://github.com/cyu/rack-cors/commit/42ebe6caa8e85ffa9c8a171bda668ba1acc7a5e6 | Patch Third Party Advisory |
http://seclists.org/fulldisclosure/2017/Jul/22 | Mailing List Third Party Advisory |
http://www.debian.org/security/2017/dsa-3931 | Third Party Advisory |
Information
Published : 2017-07-12 20:29
Updated : 2020-03-03 11:16
NVD link : CVE-2017-11173
Mitre link : CVE-2017-11173
JSON object : View
CWE
Products Affected
debian
- debian_linux
rack-cors_project
- rack-cors