Skip to content

Commit ca8a7fe

Browse files
jasnowRubySec CI
authored andcommitted
Updated advisory posts against rubysec/ruby-advisory-db@351d21d
1 parent e645113 commit ca8a7fe

File tree

1 file changed

+63
-0
lines changed

1 file changed

+63
-0
lines changed
Lines changed: 63 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,63 @@
1+
---
2+
layout: advisory
3+
title: 'CVE-2025-57821 (google_sign_in): Google Sign-In for Rails allowed redirects
4+
to malformed URLs'
5+
comments: false
6+
categories:
7+
- google_sign_in
8+
advisory:
9+
gem: google_sign_in
10+
cve: 2025-57821
11+
ghsa: 7pwc-wh6m-44q3
12+
url: https://github.com/basecamp/google_sign_in/security/advisories/GHSA-7pwc-wh6m-44q3
13+
title: Google Sign-In for Rails allowed redirects to malformed URLs
14+
date: 2025-08-27
15+
description: |
16+
### Summary
17+
18+
It is possible to craft a malformed URL that passes the "same origin"
19+
check, resulting in the user being redirected to another origin.
20+
21+
### Details
22+
23+
The google_sign_in gem persists an optional URL for redirection after
24+
authentication. If this URL is malformed, it's possible for the user
25+
to be redirected to another origin after authentication, possibly
26+
resulting in exposure of authentication information such as the token.
27+
28+
Normally the value of this URL is only written and read by the library.
29+
If applications are configured to store session information in a
30+
database, there is no known vector to exploit this vulnerability.
31+
However, applications may be configured to store this information
32+
in a session cookie, in which case it may be chained with a session
33+
cookie attack to inject a crafted URL.
34+
35+
### Impact
36+
37+
Rails applications configured to store the `flash` information in
38+
a session cookie may be vulnerable, if this can be chained with an
39+
attack that allows injection of arbitrary data into the session cookie.
40+
41+
### Workarounds
42+
43+
If you are unable to upgrade this library, then you may mitigate
44+
the chained attack by explicitly setting `SameSite=Lax` or
45+
`SameSite=Strict` on the application session cookie.
46+
47+
### Credits
48+
49+
This issue was responsibly reported by Hackerone user
50+
[muntrive](https://hackerone.com/muntrive?type=user).
51+
cvss_v3: 4.2
52+
patched_versions:
53+
- ">= 1.3.0"
54+
related:
55+
url:
56+
- https://nvd.nist.gov/vuln/detail/CVE-2025-57821
57+
- https://github.com/basecamp/google_sign_in/security/advisories/GHSA-7pwc-wh6m-44q3
58+
- https://github.com/basecamp/google_sign_in/releases/tag/v1.3.0
59+
- https://github.com/basecamp/google_sign_in/commit/a0548a604fb17e4eb1a57029f0d87e34e8499623
60+
- https://github.com/basecamp/google_sign_in/pull/73
61+
- https://github.com/basecamp/google_sign_in/commit/85903651201257d4f14b97d4582e6d968ac32f15
62+
- https://github.com/advisories/GHSA-7pwc-wh6m-44q3
63+
---

0 commit comments

Comments
 (0)