Basecamp's Google Sign-In adds Google sign-in to Rails applications. Prior to version 1.3.0, it is possible to craft a malformed URL that passes the "same origin" check, resulting in the user being redirected to another origin. Rails applications configured to store the flash information in a session cookie may be vulnerable, if this can be chained with an attack that allows injection of arbitrary data into the session cookie. This issue has been patched in version 1.3.0. If upgrading is not possible at this time, a way to mitigate the chained attack can be done by explicitly setting SameSite=Lax or SameSite=Strict on the application session cookie.
Metrics
Affected Vendors & Products
References
History
Wed, 27 Aug 2025 22:00:00 +0000
Type | Values Removed | Values Added |
---|---|---|
First Time appeared |
Basecamp
Basecamp basecamp |
|
Vendors & Products |
Basecamp
Basecamp basecamp |
Wed, 27 Aug 2025 19:15:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Metrics |
ssvc
|
Wed, 27 Aug 2025 16:45:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Description | Basecamp's Google Sign-In adds Google sign-in to Rails applications. Prior to version 1.3.0, it is possible to craft a malformed URL that passes the "same origin" check, resulting in the user being redirected to another origin. Rails applications configured to store the flash information in a session cookie may be vulnerable, if this can be chained with an attack that allows injection of arbitrary data into the session cookie. This issue has been patched in version 1.3.0. If upgrading is not possible at this time, a way to mitigate the chained attack can be done by explicitly setting SameSite=Lax or SameSite=Strict on the application session cookie. | |
Title | Basecamp's Google Sign-In for Rails allowed redirects to a malformed URL | |
Weaknesses | CWE-601 | |
References |
| |
Metrics |
cvssV3_1
|

Status: PUBLISHED
Assigner: GitHub_M
Published: 2025-08-27T16:32:36.284Z
Updated: 2025-08-27T18:53:03.636Z
Reserved: 2025-08-20T14:30:35.011Z
Link: CVE-2025-57821

Updated: 2025-08-27T17:11:44.185Z

Status : Awaiting Analysis
Published: 2025-08-27T17:15:48.057
Modified: 2025-08-29T16:24:09.860
Link: CVE-2025-57821

No data.