Atlassian Crowd CVE-2017-18107 Cross Site Request Forgery Vulnerability

Description

Atlassian Crowd is prone to a cross-site request-forgery vulnerability because it fails to properly validate HTTP requests. Exploiting this issue allows a remote attacker to perform certain unauthorized actions and gain access to the affected application. Other attacks are also possible. Versions prior to Atlassian Crowd 3.1.1 are vulnerable.

Technologies Affected

• Atlassian Crowd 0.3.3
• Atlassian Crowd 1.0.0
• Atlassian Crowd 1.0.1
• Atlassian Crowd 1.0.2
• Atlassian Crowd 1.0.3
• Atlassian Crowd 1.0.4
• Atlassian Crowd 1.0.5
• Atlassian Crowd 1.0.6
• Atlassian Crowd 1.0.7
• Atlassian Crowd 1.1.0
• Atlassian Crowd 1.1.1
• Atlassian Crowd 1.1.2
• Atlassian Crowd 1.2
• Atlassian Crowd 1.2.1
• Atlassian Crowd 1.2.4
• Atlassian Crowd 1.3
• Atlassian Crowd 1.3.1
• Atlassian Crowd 1.3.2
• Atlassian Crowd 1.3.3
• Atlassian Crowd 1.4
• Atlassian Crowd 1.4.1
• Atlassian Crowd 1.4.2
• Atlassian Crowd 1.4.3
• Atlassian Crowd 1.4.4
• Atlassian Crowd 1.4.7
• Atlassian Crowd 1.4.8
• Atlassian Crowd 1.5
• Atlassian Crowd 1.5.1
• Atlassian Crowd 1.5.2
• Atlassian Crowd 1.5.3
• Atlassian Crowd 1.6
• Atlassian Crowd 1.6.1
• Atlassian Crowd 1.6.3
• Atlassian Crowd 2.0.1
• Atlassian Crowd 2.0.2
• Atlassian Crowd 2.0.3
• Atlassian Crowd 2.0.4
• Atlassian Crowd 2.0.5
• Atlassian Crowd 2.0.6
• Atlassian Crowd 2.0.7
• Atlassian Crowd 2.0.9
• Atlassian Crowd 2.1.0
• Atlassian Crowd 2.1.1
• Atlassian Crowd 2.1.2
• Atlassian Crowd 2.10.1
• Atlassian Crowd 2.10.3
• Atlassian Crowd 2.11.0
• Atlassian Crowd 2.11.1
• Atlassian Crowd 2.2.2
• Atlassian Crowd 2.2.4
• Atlassian Crowd 2.2.7
• Atlassian Crowd 2.2.9
• Atlassian Crowd 2.3.1
• Atlassian Crowd 2.3.2
• Atlassian Crowd 2.3.3
• Atlassian Crowd 2.3.4
• Atlassian Crowd 2.3.6
• Atlassian Crowd 2.3.7
• Atlassian Crowd 2.3.8
• Atlassian Crowd 2.4
• Atlassian Crowd 2.4.1
• Atlassian Crowd 2.4.2
• Atlassian Crowd 2.4.9
• Atlassian Crowd 2.5.0
• Atlassian Crowd 2.5.1
• Atlassian Crowd 2.5.2
• Atlassian Crowd 2.5.3
• Atlassian Crowd 2.5.4
• Atlassian Crowd 2.6.0
• Atlassian Crowd 2.6.1
• Atlassian Crowd 2.6.2
• Atlassian Crowd 2.6.3
• Atlassian Crowd 2.7
• Atlassian Crowd 2.8.3
• Atlassian Crowd 2.8.8
• Atlassian Crowd 2.9.0
• Atlassian Crowd 2.9.1
• Atlassian Crowd 2.9.2
• Atlassian Crowd 2.9.3
• Atlassian Crowd 2.9.4
• Atlassian Crowd 2.9.5
• Atlassian Crowd 2.9.7
• Atlassian Crowd 3.0.4
• Atlassian Crowd 3.0.5
• Atlassian Crowd 3.1.0

Recommendations

Block external access at the network boundary, unless external parties require service.
If global access isn’t needed, filter access to the affected computer at the network boundary. Restricting access to only trusted computers and networks might greatly reduce the likelihood of successful exploits

Deploy network intrusion detection systems to monitor network traffic for malicious activity.
Deploy NIDS to detect and block attacks and anomalous activity such as requests containing suspicious URI sequences. Since the webserver may log such requests, review its logs regularly.

Do not follow links provided by unknown or untrusted sources.
Web users should be cautious about following links to sites that are provided by unfamiliar or suspicious sources. Filtering HTML from emails may help remove a possible vector for transmitting malicious links to users.

When possible, limit the privileges granted to users to the least amount required.
Ensure that all users are granted the least amount of privileges required to successfully operate.

Updates are available. Please see the references or vendor advisory for more information.