Security readout for executives and security teams
Plain-English summary
Older Atlassian Jira versions contain an open redirect in ChangeSharedFilterOwner. A remote attacker could redirect users and, in some cases, obtain a user's CSRF token. This is mainly a user-targeting risk, not documented here as direct server compromise.
Executive priority
Treat as a moderate-priority patching item for Jira. It can support phishing-like user attacks and possible CSRF token theft, but the provided sources do not show active exploitation or broader system compromise.
Technical view
CVE-2019-11589 affects Jira before 7.13.6, 8.0.0 before 8.2.3, and 8.3.0 before 8.3.2. The vulnerable ChangeSharedFilterOwner resource permits open redirect behavior that can support attacks against users and possible CSRF token exposure.
Likely exposure
Exposure is likely limited to Atlassian Jira instances running the listed vulnerable versions and reachable by potential attackers or targeted users.
Exploitation context
The source bundle provides no evidence of active exploitation, and KEV is false. The described attack requires abusing an open redirect to target users, with CSRF token exposure possible only in some cases.
Researcher notes
Evidence is limited to the CVE description and Atlassian issue reference. No CVSS vector, CWE, exploit confirmation, or detailed mitigation beyond fixed version ranges is present in the supplied bundle.
Mitigation direction
- Upgrade affected Jira deployments to 7.13.6, 8.2.3, 8.3.2, or later as applicable.
- Review Atlassian JRASERVER-69780 for vendor-specific remediation guidance.
- Prioritize externally reachable or broadly used Jira instances.
- Increase user awareness around unexpected Jira links until remediation is complete.
Validation and detection
- Inventory Jira versions across production, staging, and internal deployments.
- Compare versions against the vulnerable ranges listed in the CVE record.
- Confirm remediation by verifying the installed fixed Jira version.
- Check access logs for suspicious ChangeSharedFilterOwner requests if logs are available.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
Credential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2019-11589 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://jira.atlassian.com/browse/JRASERVER-69780CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.