CVE-2022-36800
First published: Wed Aug 03 2022(Updated: )
Affected versions of Atlassian Jira Service Management Server and Data Center allow remote attackers without the "Browse Users" permission to view groups via an Information Disclosure vulnerability in the browsegroups.action endpoint. The affected versions are before version 4.22.2.
Credit: security@atlassian.com security@atlassian.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Atlassian Jira Service Management | <4.22.2 | |
| Atlassian Jira Service Management | <4.22.2 |
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 vulnerability ID?
The vulnerability ID is CVE-2022-36800.
What is the severity of CVE-2022-36800?
The severity of CVE-2022-36800 is medium with a CVSS score of 4.3.
How does CVE-2022-36800 impact Atlassian Jira Service Management?
CVE-2022-36800 allows remote attackers without the "Browse Users" permission to view groups, leading to an information disclosure vulnerability.
Which versions of Atlassian Jira Service Management are affected by CVE-2022-36800?
The affected versions of Atlassian Jira Service Management are before version 4.22.2 for both the Server and Data Center editions.
How can CVE-2022-36800 be fixed?
To fix CVE-2022-36800, it is recommended to upgrade Atlassian Jira Service Management to version 4.22.2 or later.
- collector/nvd-index
- agent/author
- agent/type
- agent/softwarecombine
- agent/references
- agent/severity
- agent/description
- agent/first-publish-date
- agent/event
- collector/mitre-cve
- source/MITRE
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/weakness
- agent/tags
- agent/last-modified-date
- vendor/atlassian
- canonical/atlassian jira service management