Multiple cross-site request forgery (CSRF) vulnerabilities in Support Incident Tracker (aka SiT!) before 3.65 allow remote attackers to hijack the authentication of administrators for requests that change administrator email, add a new administrator, or insert arbitrary script via (1) user_profile_edit.php or (2) user_add.php.
Weakness
The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Support_incident_tracker | Sitracker | * | 3.64 (including) |
| Support_incident_tracker | Sitracker | 3.6 (including) | 3.6 (including) |
| Support_incident_tracker | Sitracker | 3.21 (including) | 3.21 (including) |
| Support_incident_tracker | Sitracker | 3.22 (including) | 3.22 (including) |
| Support_incident_tracker | Sitracker | 3.22pl1 (including) | 3.22pl1 (including) |
| Support_incident_tracker | Sitracker | 3.23 (including) | 3.23 (including) |
| Support_incident_tracker | Sitracker | 3.24 (including) | 3.24 (including) |
| Support_incident_tracker | Sitracker | 3.24-beta-2 (including) | 3.24-beta-2 (including) |
| Support_incident_tracker | Sitracker | 3.30 (including) | 3.30 (including) |
| Support_incident_tracker | Sitracker | 3.30-beta2 (including) | 3.30-beta2 (including) |
| Support_incident_tracker | Sitracker | 3.31 (including) | 3.31 (including) |
| Support_incident_tracker | Sitracker | 3.32 (including) | 3.32 (including) |
| Support_incident_tracker | Sitracker | 3.33 (including) | 3.33 (including) |
| Support_incident_tracker | Sitracker | 3.35 (including) | 3.35 (including) |
| Support_incident_tracker | Sitracker | 3.35-beta1 (including) | 3.35-beta1 (including) |
| Support_incident_tracker | Sitracker | 3.36 (including) | 3.36 (including) |
| Support_incident_tracker | Sitracker | 3.40 (including) | 3.40 (including) |
| Support_incident_tracker | Sitracker | 3.40-beta1 (including) | 3.40-beta1 (including) |
| Support_incident_tracker | Sitracker | 3.41 (including) | 3.41 (including) |
| Support_incident_tracker | Sitracker | 3.45 (including) | 3.45 (including) |
| Support_incident_tracker | Sitracker | 3.45-beta1 (including) | 3.45-beta1 (including) |
| Support_incident_tracker | Sitracker | 3.50 (including) | 3.50 (including) |
| Support_incident_tracker | Sitracker | 3.50-beta1 (including) | 3.50-beta1 (including) |
| Support_incident_tracker | Sitracker | 3.51 (including) | 3.51 (including) |
| Support_incident_tracker | Sitracker | 3.60 (including) | 3.60 (including) |
| Support_incident_tracker | Sitracker | 3.61 (including) | 3.61 (including) |
| Support_incident_tracker | Sitracker | 3.62 (including) | 3.62 (including) |
| Support_incident_tracker | Sitracker | 3.63 (including) | 3.63 (including) |
| Support_incident_tracker | Sitracker | 3.63-beta1 (including) | 3.63-beta1 (including) |
Potential Mitigations
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid [REF-1482].
- For example, use anti-CSRF packages such as the OWASP CSRFGuard. [REF-330]
- Another example is the ESAPI Session Management control, which includes a component for CSRF. [REF-45]
- Use the “double-submitted cookie” method as described by Felten and Zeller:
- When a user visits a site, the site should generate a pseudorandom value and set it as a cookie on the user’s machine. The site should require every form submission to include this value as a form value and also as a cookie value. When a POST request is sent to the site, the request should only be considered valid if the form value and the cookie value are the same.
- Because of the same-origin policy, an attacker cannot read or modify the value stored in the cookie. To successfully submit a form on behalf of the user, the attacker would have to correctly guess the pseudorandom value. If the pseudorandom value is cryptographically strong, this will be prohibitively difficult.
- This technique requires Javascript, so it may not work for browsers that have Javascript disabled. [REF-331]
Related Attack Patterns
- https://cwe.mitre.org/data/definitions/111.html
- https://cwe.mitre.org/data/definitions/462.html
- https://cwe.mitre.org/data/definitions/467.html
- https://cwe.mitre.org/data/definitions/62.html
References
- http://secunia.com/advisories/46019
- http://sitracker.org/wiki/ReleaseNotes365
- http://www.securityfocus.com/archive/1/519636
- https://www.htbridge.ch/advisory/multiple_vulnerabilities_in_sit_support_incident_tracker.html
- http://secunia.com/advisories/46019
- http://sitracker.org/wiki/ReleaseNotes365
- http://www.securityfocus.com/archive/1/519636
- https://www.htbridge.ch/advisory/multiple_vulnerabilities_in_sit_support_incident_tracker.html