CVE-2017-18107: CSRF
First published: Thu Feb 07 2019(Updated: )
Various resources in the Crowd Demo application of Atlassian Crowd before version 3.1.1 allow remote attackers to modify add, modify and delete users & groups via a Cross-site request forgery (CSRF) vulnerability. Please be aware that the Demo application is not enabled by default.
Credit: security@atlassian.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Atlassian Crowd | <3.1.1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2017-18107?
CVE-2017-18107 is classified as a medium severity Cross-site request forgery (CSRF) vulnerability.
How do I fix CVE-2017-18107?
To fix CVE-2017-18107, update Atlassian Crowd to version 3.1.1 or later.
What types of attacks are possible with CVE-2017-18107?
CVE-2017-18107 allows remote attackers to modify, add, or delete users and groups due to CSRF vulnerabilities.
Which versions of Atlassian Crowd are affected by CVE-2017-18107?
CVE-2017-18107 affects Atlassian Crowd versions prior to 3.1.1.
Is the vulnerability CVE-2017-18107 present in the default installation?
The vulnerability CVE-2017-18107 is present in the Crowd Demo application, which is not enabled by default.
- collector/nvd-index
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/author
- agent/weakness
- agent/references
- agent/last-modified-date
- agent/description
- agent/tags
- agent/first-publish-date
- agent/event
- agent/source
- vendor/atlassian
- canonical/atlassian crowd