Описание
Ability to forge per-form CSRF tokens in Rails
It is possible to, given a global CSRF token such as the one present in the authenticity_token meta tag, forge a per-form CSRF token for any action for that session.
Impact
Given the ability to extract the global CSRF token, an attacker would be able to construct a per-form CSRF token for that session.
Workarounds
This is a low-severity security issue. As such, no workaround is necessarily until such time as the application can be upgraded.
Ссылки
- https://nvd.nist.gov/vuln/detail/CVE-2020-8166
- https://hackerone.com/reports/732415
- https://github.com/rubysec/ruby-advisory-db/blob/master/gems/actionpack/CVE-2020-8166.yml
- https://groups.google.com/forum/#!topic/rubyonrails-security/NOjKiGeXUgw
- https://groups.google.com/g/rubyonrails-security/c/NOjKiGeXUgw
- https://www.debian.org/security/2020/dsa-4766
Пакеты
actionpack
>= 5.0.0, <= 5.2.4.2
5.2.4.3
actionpack
>= 6.0.0, <= 6.0.3
6.0.3.1
Связанные уязвимости
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.
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.
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.
A CSRF forgery vulnerability exists in rails < 5.2.5, rails < 6.0.4 th ...
