Security readout for executives and security teams
Plain-English summary
CVE-2019-11585 is an open redirect in Atlassian Jira's startup.jsp page. A remote attacker could craft a Jira link that sends users to another website, supporting phishing. The source bundle does not indicate code execution, data theft by itself, or confirmed active exploitation.
Executive priority
Treat as a phishing-enablement issue, not a standalone system compromise based on available evidence. Prioritize upgrade if Jira is public-facing or widely trusted by employees and customers.
Technical view
Jira versions before 7.13.6, 8.0.0 before 8.2.3, and 8.3.0 before 8.3.2 allow remote attackers to redirect users through startup.jsp. The issue is described as an open redirect usable in phishing. CVSS, CWE, and detailed exploit prerequisites are not provided in the bundle.
Likely exposure
Exposure is most relevant for organizations running affected Jira Server versions, especially internet-accessible Jira instances or environments where users trust Jira links in email, chat, or tickets.
Exploitation context
The bundle does not show KEV listing or active exploitation evidence. The practical risk is phishing: attackers may abuse trusted Jira URLs to route users to malicious destinations.
Researcher notes
The source evidence is narrow: affected version ranges and open redirect impact are stated, but CVSS, CWE, parameters, and exploitation evidence are absent. Avoid assuming broader Jira compromise from this CVE alone.
Mitigation direction
- Upgrade Jira to a fixed version: 7.13.6, 8.2.3, 8.3.2, or later.
- Review Atlassian issue JRASERVER-69784 for vendor-specific guidance.
- Limit public access to Jira where business requirements allow.
- Train users to verify final destinations before authenticating from Jira links.
Validation and detection
- Inventory Jira Server versions and compare them with the affected ranges.
- Confirm startup.jsp behavior is remediated after upgrading.
- Review web logs for unusual startup.jsp requests involving external redirection patterns.
- Check whether Jira is reachable from the internet or only internal networks.
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.
CVE-2019-11585 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-69784CVE 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.