S4E just found a high-severity finding from top 10 tcp port service scan
PlatformPlansPartners
Resources
ToolsBlogDocs
Sign Up →
medium·Product Based Web Vulnerabilities·Updated Oct 8, 2024

CVE-2024-24763 Scanner

CVE-2024-24763 Scanner - Open Redirect vulnerability in JumpServer

Est. Time~10 seconds
Scan TypeSingle Scan
Targetsdomain, ipv4, subdomain
CostFree
2.7k
Times Used
continuous scan runs
5.9k
Continuously Checked
assets under CS
0
Vulnerabilities Found
confirmed findings
References
CVECVE-2024-24763
6.1
CVSSmedium
Exploitable remotely over the internet · no authentication required · user interaction needed.

JumpServer is an open source bastion host and an operation and maintenance security audit system. Prior to version 3.10.0, attackers can exploit this vulnerability to construct malicious links, leading users to click on them, thereby facilitating phishing attacks or cross-site scripting attacks. Version 3.10.0 contains a patch for this issue. No known workarounds are available.

Attack Vector
Network
Privileges Req.
None
User Interaction
Required
Affected
jumpserverby jumpserver
< 3.10.0
Updated Aug 22, 2026View on NVD →
Detail

JumpServer is widely used by IT administrators and security professionals as a bastion host to manage and control access to critical resources, ensuring operation and maintenance security. The platform provides robust audit capabilities, allowing teams to monitor and record operations within their network environment. Its open-source nature allows for customization and adaptability to various enterprise needs. Organizations utilize JumpServer to secure remote access, enforce compliance, and maintain operational efficiency. Additionally, it helps in reducing the attack surface by consolidating access points and enhancing visibility over network activities. The JumpServer platform also supports integration with various authentication systems, ensuring secured user management.

The Open Redirect vulnerability in JumpServer allows attackers to redirect users to malicious websites by crafting specific URLs. This security flaw is due to inadequate validation of user-supplied input, which can be manipulated to divert traffic. Once a user clicks on the malicious link, they could be redirected to deceptive websites used for phishing attacks. This vulnerability poses significant risks, especially in environments where users interact with the bastion host frequently. The issue underscores the importance of input validation and secure redirection mechanisms to thwart phishing exploits. By exploiting this vulnerability, attackers can manipulate trust relationships, executing further attacks without the user's awareness.

The vulnerability in JumpServer revolves around its login redirection parameter, which can be exploited by specifying arbitrary domains. Technical analysis reveals that the vulnerable endpoints include URL paths such as 'core/auth/login/?next=//oast.me'. The pattern indicates a lack of filtering for potentially harmful URLs in the redirection logic. Attackers can leverage this by embedding unauthorized URLs within legitimate login requests. The regex matching criteria verify headers for patterns leading to unintended redirects. This flaw highlights the necessity for strict validations and the potential consequences of improper URL handling within web applications.

Exploiting this vulnerability could lead to unauthorized redirections, potentially causing users to land on malicious websites. This can facilitate phishing attacks, where attackers impersonate legitimate services to steal sensitive information like passwords and personal data. Users may inadvertently share credentials or personal details, considering they are interacting with a trusted platform. Over time, exploitation can erode trust in the application’s security, leading to reputational damage. Such vulnerabilities may also serve as a stepping stone for advanced persistent threats, further compromising organizational security.

REFERENCES

Solution Advice
  • Upgrade JumpServer to version 3.10.0 or later, where the vulnerability is patched.
  • Implement strict input validation for all user-supplied URL parameters to prevent URL manipulation.
  • Use server-side controls to verify and sanitize redirect requests to ensure they only lead to known, safe URLs.
  • Regularly review and test code for proper redirect mechanisms and incorporate security best practices.
  • Educate users about the risks of phishing and encourage them to verify URLs before clicking.

Get AI-powered remediation steps tailored to your asset.

Try AI Solutions →

Check your infrastructure.
Right now.

11,000+ scanners. Free to start. No credit card required.