Kuzmany

Users with webhook permissions can conduct Server-Side Request Forgery (SSRF) via webhooks. If they have permission to view the webhook logs, the partial request response is also disclosed. This allows bypassing firewalls to interact with internal services.

A user with administrator rights can modify the application’s configuration and extract sensitive information that is normally inaccessible. This allows an administrator to disclose parameters, such as database credentials, to which they should not have access.

A Cross-Site Scripting (XSS) vulnerability allows an attacker to execute arbitrary JavaScript in the context of another user’s session. This occurs because user-supplied input is reflected back in the server’s response without proper sanitization or escaping, potentially enabling malicious actions such as session hijacking, credential theft, or unauthorized actions in the application. The vulnerability resides in the “Tags” input field on the `/s/ajax?action=lead:addLeadTags` endpoint. Although the server applies sanitization before storing the data or returning it later, the payload is executed immediately in the victim’s browser upon reflection, allowing an attacker to run arbitrary JavaScript in the user’s session. A Reflected XSS attack can have a significant impact, allowing attackers to steal sensitive user data like cookies, redirect users to malicious websites, and manipulate the web page content.

The attacker can validate if a user exists by checking the time login returns. This timing difference can be used to enumerate valid usernames, after which an attacker could attempt brute force attacks. The issue was caused by different response times when a valid username was provided (password hashing occurred) and when an invalid username was provided (no password hashing occurred). The fix introduces a TimingSafeFormLoginAuthenticator that performs a dummy password hash verification even for non-existent users, ensuring consistent timing.