Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2023-28370: Open redirect in tornadoweb Tornado

0
Medium
VulnerabilityCVE-2023-28370cvecve-2023-28370
Published: Thu May 25 2023 (05/25/2023, 00:00:00 UTC)
Source: CVE Database V5
Vendor/Project: tornadoweb
Product: Tornado

Description

Open redirect vulnerability in Tornado versions 6.3.1 and earlier allows a remote unauthenticated attacker to redirect a user to an arbitrary web site and conduct a phishing attack by having user access a specially crafted URL.

AI-Powered Analysis

AILast updated: 11/04/2025, 00:12:07 UTC

Technical Analysis

CVE-2023-28370 is an open redirect vulnerability identified in Tornado, a widely used Python web framework, specifically affecting versions 6.3.1 and earlier. The vulnerability arises from insufficient validation of URL parameters that control redirection destinations within Tornado-based applications. An attacker can craft a malicious URL that appears to originate from a trusted Tornado web application but redirects the user to an arbitrary external site controlled by the attacker. This can facilitate phishing attacks by leveraging the trust users place in the legitimate domain, potentially leading to credential theft, malware installation, or other social engineering exploits. The vulnerability requires no authentication, making it accessible to any remote attacker, but does require user interaction to follow the malicious link. The CVSS 3.1 base score is 6.1, reflecting a medium severity level due to the ease of exploitation (network vector, low attack complexity, no privileges required) and the impact on confidentiality and integrity, but no direct impact on availability. No public exploits have been reported yet, but the vulnerability is classified under CWE-601 (Open Redirect). Tornado is commonly used in web applications and services, so the vulnerability’s impact depends on the deployment context and user base. The vulnerability was published on May 25, 2023, and no official patch links were provided at the time of reporting, indicating the need for vigilance and proactive mitigation by users of affected versions.

Potential Impact

For European organizations, the open redirect vulnerability poses a significant phishing risk, potentially undermining user trust and leading to credential compromise or malware infections. Organizations relying on Tornado for web applications, especially those handling sensitive user data or financial transactions, could face reputational damage and regulatory scrutiny under GDPR if user data is compromised. The vulnerability’s exploitation could facilitate targeted phishing campaigns against employees or customers, increasing the likelihood of successful social engineering attacks. Since Tornado is used in various sectors including finance, healthcare, and government services, the impact could extend to critical infrastructure and services. The lack of authentication requirement and ease of exploitation increase the threat surface, particularly for public-facing applications. Although no known exploits are currently active, the medium severity rating and potential for user deception necessitate prompt action. Failure to address this vulnerability could lead to increased phishing incidents, data breaches, and associated financial and legal consequences for European entities.

Mitigation Recommendations

1. Upgrade Tornado to the latest version once an official patch addressing CVE-2023-28370 is released. Monitor Tornado project repositories and security advisories for updates. 2. Implement strict validation and sanitization of all URL parameters used for redirection within the application code to ensure only trusted domains or relative paths are allowed. 3. Employ allowlists for redirect destinations to prevent arbitrary external URLs. 4. Use Content Security Policy (CSP) headers to restrict navigation and framing to trusted domains. 5. Educate users and employees about the risks of phishing and encourage verification of URLs before clicking links, especially those received via email or messaging platforms. 6. Monitor web server logs for suspicious redirect patterns or unusual URL parameters indicative of exploitation attempts. 7. Consider implementing multi-factor authentication (MFA) to reduce the impact of credential theft resulting from phishing. 8. If immediate patching is not possible, deploy web application firewalls (WAFs) with custom rules to detect and block suspicious redirect attempts.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
jpcert
Date Reserved
2023-05-11T00:00:00.000Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6909262dfe7723195e0b5e6e

Added to database: 11/3/2025, 10:01:17 PM

Last enriched: 11/4/2025, 12:12:07 AM

Last updated: 11/6/2025, 1:52:18 PM

Views: 3

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats