JIRA up to 7.13.5/8.2.2/8.3.1 ChangeSharedFilterOwner redirect
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.6 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as problematic has been discovered in JIRA up to 7.13.5/8.2.2/8.3.1. The impacted element is an unknown function of the component ChangeSharedFilterOwner. Such manipulation leads to redirect. This vulnerability is listed as CVE-2019-11589. The attack may be performed from remote. There is no available exploit. It is advisable to upgrade the affected component.
Details
A vulnerability, which was classified as problematic, has been found in JIRA up to 7.13.5/8.2.2/8.3.1. Affected by this issue is an unknown functionality of the component ChangeSharedFilterOwner. The manipulation with an unknown input leads to a redirect vulnerability. Using CWE to declare the problem leads to CWE-601. A web application accepts a user-controlled input that specifies a link to an external site, and uses that link in a Redirect. This simplifies phishing attacks. Impacted is integrity. CVE summarizes:
The ChangeSharedFilterOwner resource in Jira before version 7.13.6, from version 8.0.0 before version 8.2.3, and from version 8.3.0 before version 8.3.2 allows remote attackers to attack users, in some cases be able to obtain a user's Cross-site request forgery (CSRF) token, via a open redirect vulnerability.
The weakness was presented 08/23/2019. This vulnerability is handled as CVE-2019-11589 since 04/29/2019. The attack may be launched remotely. No form of authentication is required for exploitation. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1204.001.
Upgrading to version 7.13.6, 8.2.3 or 8.3.2 eliminates this vulnerability.
See VDB-140707, VDB-140706, VDB-140705 and VDB-140704 for similar entries. Once again VulDB remains the best source for vulnerability data.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.7VulDB Meta Temp Score: 5.6
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.1
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: RedirectCWE: CWE-601
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: JIRA 7.13.6/8.2.3/8.3.2
Timeline
04/29/2019 🔍08/23/2019 🔍
08/24/2019 🔍
12/01/2023 🔍
Sources
Advisory: jira.atlassian.comStatus: Not defined
CVE: CVE-2019-11589 (🔍)
GCVE (CVE): GCVE-0-2019-11589
GCVE (VulDB): GCVE-100-140708
See also: 🔍
Entry
Created: 08/24/2019 10:48Updated: 12/01/2023 14:12
Changes: 08/24/2019 10:48 (37), 08/04/2020 12:40 (17), 12/01/2023 14:12 (4)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.