CVE-2022-25803

What it actually does

The vulnerability permits an unauthenticated attacker to supply a crafted ticket search URL that causes the application to redirect the victim's browser to an arbitrary external domain under attacker control.

Why it matters to the business

Users of the ticket system may be sent to phishing or malware sites, eroding trust, enabling credential theft, and potentially leading to broader account compromise or regulatory issues in organizations relying on the platform.

How an attack unfolds

An attacker generates a malicious ticket-search link containing a redirect parameter pointing to an attacker-controlled site, then distributes the link via email or other channels; when a user clicks it, the application performs the open redirect without validation.

How to fix it

Upgrade Best Practical Request Tracker to version 5.0.3 or later; if immediate upgrade is not possible, restrict external access to the ticket search functionality and implement web application firewall rules to block suspicious redirect parameters.

How to confirm the fix worked

Confirm the installed version is 5.0.3 or newer, then attempt a ticket search URL containing an external redirect parameter and verify that the application no longer follows the redirect.

Typical attack path

1. Identify a publicly reachable Request Tracker instance running a version prior to 5.0.3
2. Craft a ticket search URL that includes an attacker-controlled redirect target
3. Distribute the link through phishing email, chat, or other user-facing channels
4. Victim authenticates or visits the link, triggering the redirect to the attacker site
5. Attacker harvests credentials or delivers malware on the landing page

How to detect it

Inspect web access logs for ticket search requests that contain unexpected external redirect parameters or unusually long query strings; correlate with successful 3xx responses to external domains.

What your security team should do

• Prioritize patching all Request Tracker instances to 5.0.3 or later within the next maintenance window
• Review and tighten URL validation logic around ticket search endpoints
• Monitor for any remaining instances older than 5.0.3 and isolate them until upgraded