Security readout for executives and security teams
Plain-English summary
CVE-2019-11587 is a Jira CSRF issue in ViewLogging resources. An attacker could cause certain Jira logging-related settings to be changed without the intended user action. The public source bundle names fixed Jira versions but does not provide CVSS, CWE, exploit details, or evidence of active exploitation.
Executive priority
Treat this as a patch and exposure-management item, not an emergency based on the provided evidence. Prioritize if Jira is internet-facing, operationally critical, or used by privileged administrators.
Technical view
Atlassian Jira before 7.13.6, 8.0.0 through before 8.2.3, and 8.3.0 through before 8.3.2 exposed ViewLogging class resources that allowed remote setting modification via CSRF. The source bundle does not specify which settings, required privileges, or exploitation preconditions beyond CSRF.
Likely exposure
Organizations running affected Jira Server versions are the likely exposure group. Risk depends on whether the affected Jira instance is reachable and whether a browser session with permission to modify the targeted settings can be abused.
Exploitation context
The source bundle marks KEV as false and provides no cited evidence of active exploitation. Because this is CSRF, exploitation generally depends on abusing a legitimate authenticated browser session rather than direct unauthenticated control.
Researcher notes
Key missing evidence: CVSS score, CWE mapping, affected setting details, privilege requirements, and exploit maturity. The safest assessment is source-limited: affected Jira versions expose ViewLogging resources to CSRF-driven setting modification.
Mitigation direction
- Upgrade Jira to 7.13.6, 8.2.3, 8.3.2, or a later fixed version.
- Check Atlassian JRASERVER-69782 for current vendor remediation guidance.
- Prioritize internet-facing or broadly accessible Jira instances first.
- Review Jira configuration for unexpected logging-related setting changes.
- Retire or isolate unsupported affected Jira versions.
Validation and detection
- Inventory Jira Server versions across production and non-production environments.
- Compare each version against the affected ranges in the CVE record.
- Confirm fixed versions are deployed after remediation.
- Review change history for unexpected ViewLogging or logging configuration changes.
- Document any remaining affected instances and compensating controls.
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-11587 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-69782CVE 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.