bettererrors prior to 2.8.0 did not implement CSRF protection for its internal requests. It also did not enforce the correct "Content-Type" header for these requests, which allowed a cross-origin "simple request" to be made without CORS protection. These together left an application with bettererrors enabled open to cross-origin attacks.
As a developer tool, bettererrors documentation strongly recommends addition only to the development
bundle group, so this vulnerability should only affect development environments. Please ensure that your project limits bettererrors to the development
group (or the non-Rails equivalent).
Starting with release 2.8.x, CSRF protection is enforced. It is recommended that you upgrade to the latest release, or minimally to "~> 2.8.3".
There are no known workarounds to mitigate the risk of using older releases of better_errors.
If you have any questions or comments about this advisory, please - Add to the discussion in bettererrors - Open an issue in bettererrors
{ "nvd_published_at": "2021-09-07T18:15:00Z", "cwe_ids": [ "CWE-352" ], "severity": "MODERATE", "github_reviewed": true, "github_reviewed_at": "2021-09-07T17:58:52Z" }