CVE Vulnerabilities


Cross-Site Request Forgery (CSRF)

Published: Nov 26, 2019 | Modified: Feb 13, 2023
CVSS 3.x
CVSS 2.x

A CSRF issue was found in JBoss Application Server 7 before 7.1.0. JBoss did not properly restrict access to the management console information (for example via the Access-Control-Allow-Origin HTTP access control flag). This can lead to unauthorized information leak if a user with admin privileges visits a specially-crafted web page provided by a remote attacker.


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
Jboss_application_server Redhat 7.0.0 7.0.0
Jboss_application_server Redhat 7.0.1 7.0.1
Jboss_application_server Redhat 7.0.2 7.0.2
Jboss_application_server Redhat 7.0.0 7.0.0
Jboss_application_server Redhat 7.0.0 7.0.0
Jboss_application_server Redhat 7.0.0 7.0.0
Jboss_application_server Redhat 7.0.0 7.0.0
Jboss_application_server Redhat 7.0.0 7.0.0

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]