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.
The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
Link | Tags |
---|---|
https://github.com/cyu/rack-cors/commit/e4d4fc362a4315808927011cbe5afcfe5486f17d | third party advisory patch |
https://github.com/cyu/rack-cors/compare/v1.0.3...v1.0.4 | third party advisory patch |
https://lists.debian.org/debian-lts-announce/2020/02/msg00004.html | third party advisory mailing list |
https://lists.debian.org/debian-lts-announce/2020/10/msg00000.html | third party advisory mailing list |
https://usn.ubuntu.com/4571-1/ | third party advisory vendor advisory |
https://www.debian.org/security/2021/dsa-4918 | third party advisory vendor advisory |