LiveActive security incident?Get immediate response
CVE Record

CVE-2023-22797: An open redirect vulnerability is fixed in Rails 7.0.4.1 with the new protection against open redirects fro...

An 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.

MediumCVSS 6.1Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This CVE describes an open redirect weakness in Rails redirect handling. An attacker could craft a link that sends a user through a trusted application to another site, which can support phishing or token theft scenarios. The provided data rates it medium severity, and it does not show known active exploitation.

Executive priority

Treat as a moderate phishing-enablement risk. Prioritize internet-facing Rails applications and authentication-related flows, but do not treat it as confirmed actively exploited based on the provided evidence.

Technical view

The issue is CWE-601 in Rails redirect_to handling when untrusted user input influences redirects. The source says a protection against open redirects could be bypassed with a carefully crafted URL. The affected-version evidence is inconsistent: it lists 7.0.4.1 while also saying the issue is fixed in 7.0.4.1.

Likely exposure

Exposure is most likely in Rails applications where redirect_to can receive user-controlled URL parameters or return paths. Public login, logout, SSO, invitation, and callback flows are typical areas to review.

Exploitation context

The CVSS vector requires user interaction and no privileges, with changed scope and low confidentiality and integrity impact. The source bundle does not include KEV listing or other evidence of active exploitation.

Researcher notes

The source bundle contains a mismatched reference URL for CVE-2023-22799, not CVE-2023-22797. Confidence is limited by inconsistent affected-version and reference evidence. Validate against the CVE record and Rails advisory before final remediation planning.

Mitigation direction

  • Check the official Rails advisory for exact affected and fixed versions.
  • Upgrade Rails according to vendor guidance once the correct fixed release is confirmed.
  • Avoid passing untrusted user input directly to redirect_to.
  • Restrict redirect destinations to known internal paths or approved hosts.
  • Review authentication and callback flows for user-controlled redirect parameters.

Validation and detection

  • Inventory Rails versions across applications and deployment artifacts.
  • Search code for redirect_to calls using request parameters or derived user input.
  • Test redirect behavior against allowed-host and internal-path expectations.
  • Confirm public routes cannot redirect to attacker-controlled external destinations.
  • Document any accepted redirect allowlists and their owners.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-601: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-22797 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.1CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N2.82.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.1Medium
CVSS 3.1 vector shape for CVE-2023-22797Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/ahttps://github.com/rails/rails7.0.4.1Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-601 · source CWE mapping

URL Redirection to Untrusted Site ('Open Redirect')

URL Redirection to Untrusted Site ('Open Redirect') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.