|Description||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.|
|Source||CVE (at NVD; CERT, LWN, oss-sec, fulldisc, bugtraq, EDB, Metasploit, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, Mageia, GitHub advisories/code/issues, web search, more)|
Vulnerable and fixed packages
The table below lists information on source packages.
|ruby-rack-cors (PTS)||buster, buster (security)||1.0.2-1+deb10u1||fixed|
|bookworm, sid, bullseye||1.1.1-1||fixed|
The information below is based on the following data on fixed versions.
[jessie] - ruby-rack-cors <not-affected> (Vulnerable code not present)