CVE-2017-11173
published 2017-07-13CVE-2017-11173: 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…
PriorityP340high8.8CVSS 3.1
AVNACLPRNUIRSUCHIHAH
EPSS
2.34%
82.0th percentile
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.
Affected
4 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | debian_linux | — | — |
| debian | ruby-rack-cors | < ruby-rack-cors 0.4.1-1 (bookworm) | ruby-rack-cors 0.4.1-1 (bookworm) |
| rack-cors_project | rack-cors | < 0.4.1 | 0.4.1 |
| rack-cors_project | rack-cors | >= 0 < 0.4.1 | 0.4.1 |
CVSS provenance
nvdv3.18.8HIGHCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
nvdv2.06.8MEDIUMAV:N/AC:M/Au:N/C:P/I:P/A:P
osv8.8HIGH
vendor_debian8.8HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
Missing Regex anchor in Rack-Cors allows malicious third party site to perform CORS request
osv·2018-07-31
CVE-2017-11173 [HIGH] Missing Regex anchor in Rack-Cors allows malicious third party site to perform CORS request
Missing Regex anchor in Rack-Cors allows malicious third party site to perform CORS request
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.
GHSA
Missing Regex anchor in Rack-Cors allows malicious third party site to perform CORS request
ghsa·2018-07-31
CVE-2017-11173 [HIGH] Missing Regex anchor in Rack-Cors allows malicious third party site to perform CORS request
Missing Regex anchor in Rack-Cors allows malicious third party site to perform CORS request
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.
OSV
CVE-2017-11173: Missing anchor in generated regex for rack-cors before 0
osv·2017-07-13·CVSS 8.8
CVE-2017-11173 [HIGH] CVE-2017-11173: Missing anchor in generated regex for rack-cors before 0
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.
Debian
CVE-2017-11173: ruby-rack-cors - Missing anchor in generated regex for rack-cors before 0.4.1 allows a malicious ...
vendor_debian·2017·CVSS 8.8
CVE-2017-11173 [HIGH] CVE-2017-11173: ruby-rack-cors - Missing anchor in generated regex for rack-cors before 0.4.1 allows a malicious ...
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.
Scope: local
bookworm: resolved (fixed in 0.4.1-1)
bullseye: resolved (fixed in 0.4.1-1)
forky: resolved (fixed in 0.4.1-1)
sid: resolved (fixed in 0.4.1-1)
trixie: resolved (fixed in 0.4.1-1)
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2017-11173 rubygem-rack-cors: Missing anchor in generated regex in rack/cors.rb#L256 may permit forged malicious requests [fedora-all]
bugzilla·2017-07-13·CVSS 8.8
CVE-2017-11173 [HIGH] CVE-2017-11173 rubygem-rack-cors: Missing anchor in generated regex in rack/cors.rb#L256 may permit forged malicious requests [fedora-all]
CVE-2017-11173 rubygem-rack-cors: Missing anchor in generated regex in rack/cors.rb#L256 may permit forged malicious requests [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit m
Bugzilla
CVE-2017-11173 rubygem-rack-cors: Missing anchor in generated regex in rack/cors.rb#L256 may permit forged malicious requests [epel-all]
bugzilla·2017-07-13·CVSS 8.8
CVE-2017-11173 [HIGH] CVE-2017-11173 rubygem-rack-cors: Missing anchor in generated regex in rack/cors.rb#L256 may permit forged malicious requests [epel-all]
CVE-2017-11173 rubygem-rack-cors: Missing anchor in generated regex in rack/cors.rb#L256 may permit forged malicious requests [epel-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of epel-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit messa
Bugzilla
CVE-2017-11173 rubygem-rack-cors: Missing anchor in generated regex in rack/cors.rb#L256 may permit forged malicious requests
bugzilla·2017-07-13·CVSS 8.8
CVE-2017-11173 [HIGH] CVE-2017-11173 rubygem-rack-cors: Missing anchor in generated regex in rack/cors.rb#L256 may permit forged malicious requests
CVE-2017-11173 rubygem-rack-cors: Missing anchor in generated regex in rack/cors.rb#L256 may permit forged malicious requests
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
Discussion:
Created rubygem-rack-cors tracking bugs for this is
http://seclists.org/fulldisclosure/2017/Jul/22http://www.debian.org/security/2017/dsa-3931https://github.com/cyu/rack-cors/commit/42ebe6caa8e85ffa9c8a171bda668ba1acc7a5e6https://packetstormsecurity.com/files/143345/rack-cors-Missing-Anchor.htmlhttp://seclists.org/fulldisclosure/2017/Jul/22http://www.debian.org/security/2017/dsa-3931https://github.com/cyu/rack-cors/commit/42ebe6caa8e85ffa9c8a171bda668ba1acc7a5e6https://packetstormsecurity.com/files/143345/rack-cors-Missing-Anchor.html
2017-07-13
Published