Stored XSS via HTML scrubber rule in RTIR
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Best Practical Solutions | RT for Incident Response | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Best Practical Solutions | Rt For Incident Response |
|
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.450% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | RTIR extends RT's HTML scrubber to allow an internal link placeholder, and the extension lets through any link that merely contains the placeholder, including links using the executable javascript: scheme. The change applies to the whole RT instance once RTIR is installed, not only to RTIR's own queues. Anyone who can add HTML content to a ticket on such an instance can store such a link. That includes an unauthenticated sender of HTML email to the Incident Reports queue, which RTIR opens to everyone by default. Script runs when a user clicks the link, in that user's session, and can act in RT with that user's authority. This issue was fixed in version 5.0.11 and 6.0.4 | |
| Title | Stored XSS via HTML scrubber rule in RTIR | |
| First Time appeared |
Best Practical Solutions
Best Practical Solutions rt For Incident Response |
|
| Weaknesses | CWE-79 | |
| CPEs | cpe:2.3:a:best_practical_solutions:rt_for_incident_response:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Best Practical Solutions
Best Practical Solutions rt For Incident Response |
|
| References |
| |
| Metrics |
cvssV4_0
|