CVE Vulnerabilities

CVE-2015-5351

Cross-Site Request Forgery (CSRF)

Published: Feb 25, 2016 | Modified: Dec 08, 2023
CVSS 3.x
8.8
HIGH
Source:
NVD
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
CVSS 2.x
6.8 MEDIUM
AV:N/AC:M/Au:N/C:P/I:P/A:P
RedHat/V2
4.4 MODERATE
AV:L/AC:M/Au:N/C:P/I:P/A:P
RedHat/V3
8.8 MODERATE
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Ubuntu
MEDIUM

The (1) Manager and (2) Host Manager applications in Apache Tomcat 7.x before 7.0.68, 8.x before 8.0.31, and 9.x before 9.0.0.M2 establish sessions and send CSRF tokens for arbitrary new requests, which allows remote attackers to bypass a CSRF protection mechanism by using a token.

Weakness

The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request.

Affected Software

Name Vendor Start Version End Version
Tomcat Apache 7.0.0-beta (including) 7.0.0-beta (including)
Tomcat Apache 7.0.2-beta (including) 7.0.2-beta (including)
Tomcat Apache 7.0.4-beta (including) 7.0.4-beta (including)
Tomcat Apache 7.0.5-beta (including) 7.0.5-beta (including)
Tomcat Apache 7.0.6 (including) 7.0.6 (including)
Tomcat Apache 7.0.10 (including) 7.0.10 (including)
Tomcat Apache 7.0.11 (including) 7.0.11 (including)
Tomcat Apache 7.0.12 (including) 7.0.12 (including)
Tomcat Apache 7.0.14 (including) 7.0.14 (including)
Tomcat Apache 7.0.16 (including) 7.0.16 (including)
Tomcat Apache 7.0.19 (including) 7.0.19 (including)
Tomcat Apache 7.0.20 (including) 7.0.20 (including)
Tomcat Apache 7.0.21 (including) 7.0.21 (including)
Tomcat Apache 7.0.22 (including) 7.0.22 (including)
Tomcat Apache 7.0.23 (including) 7.0.23 (including)
Tomcat Apache 7.0.25 (including) 7.0.25 (including)
Tomcat Apache 7.0.26 (including) 7.0.26 (including)
Tomcat Apache 7.0.27 (including) 7.0.27 (including)
Tomcat Apache 7.0.28 (including) 7.0.28 (including)
Tomcat Apache 7.0.29 (including) 7.0.29 (including)
Tomcat Apache 7.0.30 (including) 7.0.30 (including)
Tomcat Apache 7.0.32 (including) 7.0.32 (including)
Tomcat Apache 7.0.33 (including) 7.0.33 (including)
Tomcat Apache 7.0.34 (including) 7.0.34 (including)
Tomcat Apache 7.0.35 (including) 7.0.35 (including)
Tomcat Apache 7.0.37 (including) 7.0.37 (including)
Tomcat Apache 7.0.39 (including) 7.0.39 (including)
Tomcat Apache 7.0.40 (including) 7.0.40 (including)
Tomcat Apache 7.0.41 (including) 7.0.41 (including)
Tomcat Apache 7.0.42 (including) 7.0.42 (including)
Tomcat Apache 7.0.47 (including) 7.0.47 (including)
Tomcat Apache 7.0.50 (including) 7.0.50 (including)
Tomcat Apache 7.0.52 (including) 7.0.52 (including)
Tomcat Apache 7.0.53 (including) 7.0.53 (including)
Tomcat Apache 7.0.54 (including) 7.0.54 (including)
Tomcat Apache 7.0.55 (including) 7.0.55 (including)
Tomcat Apache 7.0.56 (including) 7.0.56 (including)
Tomcat Apache 7.0.57 (including) 7.0.57 (including)
Tomcat Apache 7.0.59 (including) 7.0.59 (including)
Tomcat Apache 7.0.61 (including) 7.0.61 (including)
Tomcat Apache 7.0.62 (including) 7.0.62 (including)
Tomcat Apache 7.0.63 (including) 7.0.63 (including)
Tomcat Apache 7.0.64 (including) 7.0.64 (including)
Tomcat Apache 7.0.65 (including) 7.0.65 (including)
Tomcat Apache 7.0.67 (including) 7.0.67 (including)
Tomcat Apache 8.0.0-rc1 (including) 8.0.0-rc1 (including)
Tomcat Apache 8.0.0-rc10 (including) 8.0.0-rc10 (including)
Tomcat Apache 8.0.0-rc3 (including) 8.0.0-rc3 (including)
Tomcat Apache 8.0.0-rc5 (including) 8.0.0-rc5 (including)
Tomcat Apache 8.0.1 (including) 8.0.1 (including)
Tomcat Apache 8.0.3 (including) 8.0.3 (including)
Tomcat Apache 8.0.11 (including) 8.0.11 (including)
Tomcat Apache 8.0.12 (including) 8.0.12 (including)
Tomcat Apache 8.0.14 (including) 8.0.14 (including)
Tomcat Apache 8.0.15 (including) 8.0.15 (including)
Tomcat Apache 8.0.17 (including) 8.0.17 (including)
Tomcat Apache 8.0.18 (including) 8.0.18 (including)
Tomcat Apache 8.0.20 (including) 8.0.20 (including)
Tomcat Apache 8.0.21 (including) 8.0.21 (including)
Tomcat Apache 8.0.22 (including) 8.0.22 (including)
Tomcat Apache 8.0.23 (including) 8.0.23 (including)
Tomcat Apache 8.0.24 (including) 8.0.24 (including)
Tomcat Apache 8.0.26 (including) 8.0.26 (including)
Tomcat Apache 8.0.27 (including) 8.0.27 (including)
Tomcat Apache 8.0.28 (including) 8.0.28 (including)
Tomcat Apache 8.0.29 (including) 8.0.29 (including)
Tomcat Apache 8.0.30 (including) 8.0.30 (including)
Tomcat Apache 9.0.0-milestone1 (including) 9.0.0-milestone1 (including)
Red Hat Enterprise Linux 7 RedHat tomcat-0:7.0.69-10.el7 *
Red Hat JBoss Enterprise Web Server 2 for RHEL 6 RedHat tomcat7-0:7.0.54-23_patch_05.ep6.el6 *
Red Hat JBoss Enterprise Web Server 2 for RHEL 7 RedHat tomcat7-0:7.0.54-23_patch_05.ep6.el7 *
Red Hat JBoss Web Server 2.1 RedHat tomcat7 *
Red Hat JBoss Web Server 3.0 RedHat *
Red Hat JBoss Web Server 3 for RHEL 6 RedHat httpd24-0:2.4.6-61.ep7.el6 *
Red Hat JBoss Web Server 3 for RHEL 6 RedHat mod_security-jws3-0:2.8.0-7.GA.ep7.el6 *
Red Hat JBoss Web Server 3 for RHEL 6 RedHat tomcat7-0:7.0.59-50_patch_01.ep7.el6 *
Red Hat JBoss Web Server 3 for RHEL 6 RedHat tomcat8-0:8.0.18-61_patch_01.ep7.el6 *
Red Hat JBoss Web Server 3 for RHEL 7 RedHat httpd24-0:2.4.6-61.ep7.el7 *
Red Hat JBoss Web Server 3 for RHEL 7 RedHat mod_security-jws3-0:2.8.0-7.GA.ep7.el7 *
Red Hat JBoss Web Server 3 for RHEL 7 RedHat tomcat7-0:7.0.59-50_patch_01.ep7.el7 *
Red Hat JBoss Web Server 3 for RHEL 7 RedHat tomcat8-0:8.0.18-61_patch_01.ep7.el7 *
Tomcat6 Ubuntu trusty *
Tomcat6 Ubuntu upstream *
Tomcat6 Ubuntu wily *
Tomcat7 Ubuntu precise *
Tomcat7 Ubuntu trusty *
Tomcat7 Ubuntu upstream *
Tomcat7 Ubuntu wily *
Tomcat8 Ubuntu upstream *
Tomcat8 Ubuntu wily *

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.
  • 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]

References