You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While reviewing the code, I noticed a potential DOM-Based Cross-Site Scripting (DOM-XSS) vulnerability related to how redirection is handled via jumpPath in the client-side JavaScript.
This issue could allow an attacker to execute malicious JavaScript in a user's browser, leading to session hijacking, phishing attacks, or unauthorized actions.
Steps to Reproduce (Proof of Concept)
If an attacker can control the server response and set: jumpPath: javascript:alert('Hacked');
The following vulnerable code will execute: window.location.href = getBasePath() + xmlhttp.getResponseHeader("jumpPath");
This results in:
window.location.href = "javascript:alert('Hacked');";
The browser executes the JavaScript, leading to arbitrary code execution.
## Impact
High Severity: Allows attackers to execute malicious JavaScript in users’ browsers.
While reviewing the code, I noticed a potential DOM-Based Cross-Site Scripting (DOM-XSS) vulnerability related to how redirection is handled via jumpPath in the client-side JavaScript.
This issue could allow an attacker to execute malicious JavaScript in a user's browser, leading to session hijacking, phishing attacks, or unauthorized actions.
Steps to Reproduce (Proof of Concept)
If an attacker can control the server response and set: jumpPath: javascript:alert('Hacked');
The following vulnerable code will execute: window.location.href = getBasePath() + xmlhttp.getResponseHeader("jumpPath");
This results in:
window.location.href = "javascript:alert('Hacked');";
The browser executes the JavaScript, leading to arbitrary code execution.
## Impact
High Severity: Allows attackers to execute malicious JavaScript in users’ browsers.
Potential Risks: Account compromise, phishing, session hijacking.
Fix Priority: High 🚀
I truly appreciate the hard work of the maintainers and wanted to bring this to your attention for the security of the project and its users.
The text was updated successfully, but these errors were encountered: