First published: Thu Jul 02 2020(Updated: )
A CSRF forgery vulnerability exists in rails < 5.2.5, rails < 6.0.4 that makes it possible for an attacker to, given a global CSRF token such as the one present in the authenticity_token meta tag, forge a per-form CSRF token.
Credit: support@hackerone.com
Affected Software | Affected Version | How to fix |
---|---|---|
debian/rails | 2:5.2.2.1+dfsg-1+deb10u3 2:5.2.2.1+dfsg-1+deb10u5 2:6.0.3.7+dfsg-2+deb11u2 2:6.1.7.3+dfsg-1 2:6.1.7.3+dfsg-2 | |
Rubyonrails Rails | <5.2.4.3 | |
Rubyonrails Rails | >=6.0.0<6.0.3.1 | |
Debian Debian Linux | =10.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The vulnerability ID is CVE-2020-8166.
The severity of CVE-2020-8166 is not specified.
The software versions affected by CVE-2020-8166 are rails < 5.2.5 and rails < 6.0.4.
The CSRF forgery vulnerability in CVE-2020-8166 allows an attacker to forge a per-form CSRF token using a global CSRF token.
To fix the CSRF forgery vulnerability in rails, update to version 5.2.5 or 6.0.4 or higher.