Jira ServerApplication · Atlassian
CVE-2019-8445
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 · uneditedSeveral worklog rest resources in Jira before version 7.13.7, and from version 8.0.0 before version 8.3.2 allow remote attackers to view worklog time information via a missing permissions check.
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 confidenceThis is an information disclosure vulnerability in Atlassian Jira's worklog REST resources. The affected versions (before 7.13.7 and 8.0.0-8.3.1) lack proper permission checks on worklog endpoints, allowing remote attackers to view sensitive time-tracking data without authentication or authorization.
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
Jira ServerApplication
>= 7.13.0, < 7.13.7>= 8.0.0, < 8.3.2CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Jira Server versionCheck the installed Jira version by accessing the administration panel or checking the <jira-install>/atlassian-jira/WEB-INF/classes/application-info.xml file, or run: java -jar JiraSoftware.exe --version (or check the About page in the UI).Affected if The version falls within 7.13.0-7.13.6 or 8.0.0-8.3.1, placing it within the vulnerable range.
-
Confirm time tracking is enabledNavigate to Jira Administration > Time Tracking (or check the /rest/api/2/configuration endpoint) to verify if the time tracking feature is turned on.Affected if Time tracking is enabled, making the worklog REST endpoints relevant to the installation.
-
Test unauthenticated worklog endpoint accessSend a GET request to /rest/api/2/issue/<valid-issue-key>/worklog without providing authentication credentials or valid session cookies.Affected if The endpoint returns worklog data (HTTP 200 with JSON containing work entries) without requiring authentication, confirming the permission bypass exists.
-
Test worklog access without required permissionsUsing a low-privileged user account (or no account), attempt to access /rest/api/2/issue/<issue-key>/worklog for an issue where the user has no browse permission or is not assigned to the project.Affected if The endpoint returns worklog data despite the user lacking proper browse permissions on the issue or project.
A user is affected if their Jira Server version is 7.13.0-7.13.6 or 8.0.0-8.3.1, time tracking is enabled, and the worklog REST endpoints return sensitive time-tracking data without requiring valid authentication or proper permission validation.
Generated from the published advisory. Verify against your own configuration.
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 data7.13.78.3.2
Upgrade Jira to version 7.13.7 or 8.3.2 or later to apply the vendor patch that enforces proper permission checks on worklog REST endpoints.
Fix this in Jira Server
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA0.5 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,280.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-8445 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-8445 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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