Read the docs
TI-2022-26673 Aliases GHSA-3qmc-2r76-4rqp

Redwood is vulnerable to account takeover via dbAuth "forgot-password"

Priority LOW 38Published · Updated

Key facts

Attack vector
—
Privileges required
—
User interaction
—
Attack complexity
—
Impact type
—
Confidentiality · integrity · availability
—
Fix status
Fixed

No CVSS vector from any source. Fix status from GitHub.

Summary

# Impact _What kind of vulnerability is it? Who is impacted?_ This is an API vulnerability in Redwood's [dbAuth], specifically the dbAuth forgot password feature: - only projects with the dbAuth "forgot password" feature are affected - this vulnerability was introduced in v0.38.0 ## User Accounts are Vulnerable to Takeover (Hijacking) A reset token for any user can be obtained given knowledge of their username or email via the forgot-password API. With the leaked reset token, a malicious user could request to reset a user's password, changing their credentials and gaining access to their account. ## How to Determine if Projects have been Attacked To determine if a project has been attacked, we recommend checking logs for suspicious activity; namely, the volume of requests to the forgot-password API using emails that don't exist. Another indication is if users inform you that they can't access their accounts. If you have question or concerns, reach out via the "For More Information" section below. # Patch Releases Available **The problem has been patched on the v3 and v2 release lines.** Users should upgrade to **v3.3.1+** or **v2.2.5+** respectively. ## Workarounds _Is there a way for users to fix or remediate the vulnerability without upgrading?_ We recommend upgrading to the Patch Releases above. If upgrading is not possible, there are several workarounds: ### Manually strip out `resetToken` and `resetTokenExpiresAt` in the `forgotPassword.handler()` Users on all release lines can have their `forgotPassword.handler()` function strip out the sensitive fields manually before returning ```js handler: (user) => { // your code to notify/email user of the link to reset their password... const = { resetToken, resetTokenExpiresAt, ...rest } return rest } ``` ### Use `yarn patch` to manually apply the fix Users on v3 and v2 can use [`yarn patch`] to apply the fix if they're using yarn v3. See the dbAuth "forgot-password" Account Takeover Vulnerability high gist for instructions. ### Disable the forgot password flow entirely v3 only Users on v3 can disable the forgot password flow entirely.

Why it matters now

Fix Fixed @redwoodjs/api (npm): 2.2.5, 3.3.1

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
—@redwoodjs/api (npm)0.38.0 to before 2.2.52.2.5Patch availableGHSA-3qmc-2r76-4rqp
—@redwoodjs/api (npm)3.0.0 to before 3.3.13.3.1Patch availableGHSA-3qmc-2r76-4rqp
  • @redwoodjs/api (npm) Vendor— Affected 0.38.0 to before 2.2.5 Fixed in 2.2.5 Patch available GHSA-3qmc-2r76-4rqp
  • @redwoodjs/api (npm) Vendor— Affected 3.0.0 to before 3.3.1 Fixed in 3.3.1 Patch available GHSA-3qmc-2r76-4rqp

Remediation

  • Fix · GHSA-3qmc-2r76-4rqp @redwoodjs/api (npm) Fixed in 2.2.5 Advisory →
  • Fix · GHSA-3qmc-2r76-4rqp @redwoodjs/api (npm) Fixed in 3.3.1 Advisory →

Timeline

  1. 2026-10-03 Threatist record created from GHSA-3qmc-2r76-4rqp

References

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences