Stored XSS via related ticket subject on RTIR Split and Create Incident forms
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.410% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | RTIR's ticket creation forms show the subject of the related ticket when splitting a ticket or creating an incident from a report, and they render that subject without HTML escaping. A ticket subject containing script runs it when a user opens either form. RTIR grants everyone the right to create Incident Reports by default, so an unauthenticated sender of an emailed report can set that subject. The script then runs in the session of the incident handler who creates an incident from the report or splits it, and can act in RT with that user's authority. The issue was fixed in version 6.0.4. RTIR 5.0 is not affected. | |
| Title | Stored XSS via related ticket subject on RTIR Split and Create Incident forms | |
| 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
|