Executive Summary

This vulnerability exists in File Browser versions prior to 2.57.1 and involves a case-sensitivity flaw in the password validation logic.

Specifically, by using the field name "Password" with a capital 'P' instead of the lowercase "password" in an API request, the system bypasses the verification of the current password.

This means that any authenticated user can change their password without providing the current password, and an admin can change any user's password without the current password.

An attacker who obtains a valid JWT token through methods like cross-site scripting (XSS) or session hijacking can exploit this flaw to take over accounts.

Useful 0 Not Useful 0

Impact Analysis

This vulnerability can lead to unauthorized account takeover.

If an attacker gains access to a valid JWT token, they can change passwords without knowing the current password, potentially locking out legitimate users.

This compromises the integrity and security of user accounts, leading to potential unauthorized access to sensitive files managed by the File Browser.

Useful 0 Not Useful 0

Compliance Impact

I don't know

Useful 0 Not Useful 0

Detection Guidance

I don't know

Useful 0 Not Useful 0

Mitigation Strategies

To mitigate this vulnerability, you should upgrade File Browser to version 2.57.1 or later, where the password validation logic flaw has been fixed.

Additionally, ensure that JWT tokens are protected from theft via XSS, session hijacking, or other means to prevent account takeover.

Useful 0 Not Useful 0