ActionpackApplication · Actionpack Project
CVE-2023-22797
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn open redirect vulnerability is fixed in Rails 7.0.4.1 with the new protection against open redirects from calling redirect_to with untrusted user input. In prior versions the developer was fully responsible for only providing trusted input. However the check introduced could allow an attacker to bypass with a carefully crafted URL resulting in an open redirect vulnerability.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceAn open redirect vulnerability exists in Rails 7.0.4.1 where the newly introduced protection against redirects with untrusted user input can be bypassed using a carefully crafted URL. Attackers can exploit this to redirect users to malicious sites.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
ActionpackApplication
>= 7.0.0, < 7.0.4.1
RailsApplication
>= 7.0.0, < 7.0.4.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Rails versionRun `bundle show rails` or check the version line in your Gemfile.lock. Alternatively, in a Rails console, run `Rails.version`.Affected if The version is >= 7.0.0 and < 7.0.4.1
-
Identify Actionpack versionRun `bundle show actionpack` or check your Gemfile.lock for the actionpack gem version.Affected if The version is >= 7.0.0 and < 7.0.4.1 and you use Actionpack directly
-
Find redirect calls with user inputSearch your codebase for `redirect_to` calls that include parameters such as `params[:return_url]`, `params[:url]`, `params[:redirect]`, or similar user-controllable input. Review controllers that handle redirection.Affected if Your application uses `redirect_to` with any user-supplied parameter without additional validation
-
Check redirect whitelist logicReview your redirect handling code to see if destinations are validated against a whitelist or domain allowlist before redirection.Affected if Redirects accept arbitrary user input without explicit whitelist validation
You are affected if your Rails or Actionpack version is 7.0.0 through 7.0.4 and your application uses redirect with untrusted user-supplied URLs.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped7.0.4.1
Upgrade to the latest patched Rails version when available. Additionally, continue to validate and whitelist redirect destinations in application code rather than relying solely on the framework's built-in protection.
Rails 7.0.4.1 or later (Actionpack 7.0.4.1 or later)
- Update the Rails version in your Gemfile to 7.0.4.1 or later (e.g., gem 'rails', '~> 7.0.4' or gem 'rails', '7.0.4.1')
- Run bundle update rails to install the new version
- Review your codebase for any redirect_to calls that use user-supplied input and ensure they use safe patterns (e.g., model lookups or allowlists) rather than directly passing untrusted input
- Test your application thoroughly, especially any redirect functionality
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Actionpack
Scoped from the published advisory
- Consultation4.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-22797 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-22797 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data