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.
Advisories
Source ID Title
EUVD EUVD EUVD-2018-0207 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.
Github GHSA Github GHSA GHSA-2j9c-9vmv-7m39 Missing Regex anchor in Rack-Cors allows malicious third party site to perform CORS request
Fixes

Solution

No solution given by the vendor.


Workaround

No workaround given by the vendor.

History

No history.

cve-icon MITRE

Status: PUBLISHED

Assigner: mitre

Published:

Updated: 2024-08-05T17:57:58.552Z

Reserved: 2017-07-11T00:00:00

Link: CVE-2017-11173

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Deferred

Published: 2017-07-13T03:29:00.217

Modified: 2025-04-20T01:37:25.860

Link: CVE-2017-11173

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

No data.