Debian Ruby-Rack-Cors vulnerabilities
3 known vulnerabilities affecting debian/ruby-rack-cors.
Total CVEs
3
CISA KEV
0
Public exploits
0
Exploited in wild
0
Severity breakdown
HIGH1MEDIUM1LOW1
Vulnerabilities
Page 1 of 1
CVE-2024-27456LOWCVSS 9.12024
CVE-2024-27456 [CRITICAL] CVE-2024-27456: ruby-rack-cors - rack-cors (aka Rack CORS Middleware) 2.0.1 has 0666 permissions for the .rb file...
rack-cors (aka Rack CORS Middleware) 2.0.1 has 0666 permissions for the .rb files.
Scope: local
bookworm: resolved
bullseye: resolved
forky: resolved
sid: resolved
trixie: resolved
debian
CVE-2019-18978MEDIUMCVSS 5.3fixed in ruby-rack-cors 1.1.1-1 (bookworm)2019
CVE-2019-18978 [MEDIUM] CVE-2019-18978: ruby-rack-cors - An issue was discovered in the rack-cors (aka Rack CORS Middleware) gem before 1...
An issue was discovered in the rack-cors (aka Rack CORS Middleware) gem before 1.0.4 for Ruby. It allows ../ directory traversal to access private resources because resource matching does not ensure that pathnames are in a canonical format.
Scope: local
bookworm: resolved (fixed in 1.1.1-1)
bullseye: resolved (fixed in 1.1.1-1)
forky: resolved (fixed in 1.1
debian
CVE-2017-11173HIGHCVSS 8.8fixed in ruby-rack-cors 0.4.1-1 (bookworm)2017
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: l
debian