dbcve.org
JiraApplication · Atlassian

CVE-2019-11587

MEDIUM · 6.5 CVSS v3.0 Published 2019-08-23
Fix available
A fix is available. Upgrade to 7.13.6 / 8.2.3 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Various exposed resources of the ViewLogging class 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 allow remote attackers to modify various settings via Cross-site request forgery (CSRF).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Cross-site request forgery (CSRF) vulnerability in Jira's ViewLogging class allows remote attackers to modify various settings by tricking authenticated users into submitting malicious requests. The attack exploits the lack of anti-CSRF tokens on state-changing operations in the logging configuration endpoints.

MitigationApply the vendor patches: upgrade Jira to version 7.13.6, 8.2.3, 8.3.2 or later. Additionally, implement CSRF tokens on all state-changing endpoints as a defense-in-depth measure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
JiraApplication
Affected:< 7.13.6
Jira ServerApplication
Affected:>= 8.0.0, < 8.2.3>= 8.3.0, < 8.3.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine Jira version
    Navigate to Jira Administration > System > Troubleshooting and support tools > System Info, or check the about page at /secure/About.jspa. Alternatively, check the installation directory for a version file.
    Affected if The installed version is less than 7.13.6, OR between 8.0.0 and 8.2.2 inclusive, OR between 8.3.0 and 8.3.1 inclusive.
  2. Verify logging configuration access
    Check if the user role has access to Jira administration console and logging configuration. Navigate to System > Troubleshooting and support tools > Logging and profiling or /secure/admin/ViewLogging.jspa.
    Affected if The authenticated user role has administrative access to the logging configuration endpoints.
  3. Confirm state-changing logging operations
    Identify if any state-changing actions exist in the logging configuration, such as modifying log levels, adding appenders, or changing logging profiles.
    Affected if The logging configuration allows modifying settings (such as log levels or appenders) without requiring explicit user confirmation for each change.
  4. Check for anti-CSRF token presence
    Submit a legitimate state-changing request to the logging endpoint and examine if the request includes a CSRF token parameter (typically 'atl_token' or similar). Inspect the HTML form or AJAX requests for the presence of csrf token fields.
    Affected if State-changing operations in the logging configuration do not include anti-CSRF tokens in the request parameters.

A user is affected if they run a vulnerable Jira version (below 7.13.6, or 8.0.0-8.2.2, or 8.3.0-8.3.1) AND have administrative access to the logging configuration endpoints where state-changing operations lack CSRF protection.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 7.13.6 / 8.2.3 / 8.3.2 or later
Fixed in 7.13.68.2.38.3.2
Interim mitigation

Apply the vendor patches: upgrade Jira to version 7.13.6, 8.2.3, 8.3.2 or later. Additionally, implement CSRF tokens on all state-changing endpoints as a defense-in-depth measure.

Fix this in Jira Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-11587 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-11587 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data