Описание
Google Sign-In for Rails allowed redirect to protocol-relative URI
Summary
It is possible to redirect a user to another origin if the "proceed_to" value in the session store is set to a protocol-relative URL.
Details
The google_sign_in gem persists an optional URL for redirection after authentication. If this URL is set to a protocol-relative URL, it improperly passes the "same origin" check, and it's possible for the user to be redirected to another origin after authentication, possibly resulting in exposure of authentication information if this attack is chained with other attacks.
Normally the value of this URL is only written and read by the library or the calling application. However, it may be possible to set this session value from a malicious site with a form submission.
Impact
Any Rails applications using the google_sign_in gem may be vulnerable, if this vector can be chained with another attack that is able to modify the OAuth2 request parameters.
Workarounds
No known workarounds.
Credits
This issue was responsibly reported by Hackerone user muntrive.
Ссылки
- https://github.com/basecamp/google_sign_in/security/advisories/GHSA-5jch-xhw4-r43v
- https://nvd.nist.gov/vuln/detail/CVE-2025-58067
- https://github.com/basecamp/google_sign_in/pull/75
- https://github.com/basecamp/google_sign_in/commit/e97aef4626b1bcbd2c6f01f7dd25f12ac855d4cc
- https://github.com/basecamp/google_sign_in/releases/tag/v1.3.1
- https://github.com/rubysec/ruby-advisory-db/blob/master/gems/google_sign_in/CVE-2025-58067.yml
Пакеты
google_sign_in
< 1.3.1
1.3.1
Связанные уязвимости
Basecamp's Google Sign-In adds Google sign-in to Rails applications. Prior to version 1.3.1, it is possible to redirect a user to another origin if the "proceed_to" value in the session store is set to a protocol-relative URL. Normally the value of this URL is only written and read by the library or the calling application. However, it may be possible to set this session value from a malicious site with a form submission. Any Rails applications using the google_sign_in gem may be vulnerable, if this vector can be chained with another attack that is able to modify the OAuth2 request parameters. This issue has been patched in version 1.3.1. There are no workarounds.