CVE-2017-11173

moderate-risk
Published 2017-07-13

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.

Do I need to act?

~
1.8% chance of exploitation in next 30 days
EPSS score — moderate exploit probability
-
Not on CISA KEV list
No confirmed active exploitation reported to CISA
?
Patch status unknown
Check vendor advisories for fix availability and mitigation guidance
8
CVSS 8.8/10 High
NETWORK / LOW complexity

Affected Products (2)

Rack-Cors

Affected Vendors

Rack-Cors Project Debian

References (8)

Mailing List http://seclists.org/fulldisclosure/2017/Jul/22
Third Party Advisory http://www.debian.org/security/2017/dsa-3931
Patch https://github.com/cyu/rack-cors/commit/42ebe6caa8e85ffa9c8a171bda668ba1acc7a5e6
Third Party Advisory https://packetstormsecurity.com/files/143345/rack-cors-Missing-Anchor.html
Mailing List http://seclists.org/fulldisclosure/2017/Jul/22
Third Party Advisory http://www.debian.org/security/2017/dsa-3931
Patch https://github.com/cyu/rack-cors/commit/42ebe6caa8e85ffa9c8a171bda668ba1acc7a5e6
Third Party Advisory https://packetstormsecurity.com/files/143345/rack-cors-Missing-Anchor.html
42
/ 100
moderate-risk
Severity 30/34 · Critical
Exploitability 5/34 · Minimal
Exposure 7/34 · Low