SQL Injection in Request Tracker 4.0.10 and earlier (ShowPending parameter)
A reported SQL injection vulnerability exists in the Approvals/ component of Request Tracker (RT) versions 4.0.10 and earlier, where the ShowPending parameter is allegedly not properly sanitized, allowing remote attackers to execute arbitrary SQL commands. However, the vendor has disputed the validity of this vulnerability, stating that they were unable to replicate the issue and that the original reporter retracted their claim.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If the vulnerability were valid, successful exploitation would allow remote attackers to execute arbitrary SQL commands against the RT database, potentially leading to data exfiltration, modification, or further compromise of the application. However, the vendor's statement casts doubt on the existence and exploitability of this issue.
If you can’t patch tonight, do this now.
As a general precaution, ensure that all user-supplied input is properly sanitized and parameterized in SQL queries. Monitor vendor advisories for any updates or patches. However, the vendor has stated that this specific issue could not be reproduced.
Patch, then assume compromise.
No remediation is necessary according to the vendor, as they were unable to reproduce the issue and the original report was retracted. If concerned, users should ensure they are running the latest supported version of Request Tracker and follow secure coding practices for input validation.
No validated public exploits yet. Hidden: 1 not yet analyzed, such as Exploit-DB entries.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.