LiveActive security incident?Get immediate response
CVE Record

CVE-2019-8445: Several worklog rest resources in Jira before version 7.13.7, and from version 8.0.0 before version 8.3.2 a...

Several 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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2019-8445 is a Jira authorization flaw that could let remote attackers view worklog time information they should not be permitted to see. The issue is data exposure, not code execution, but it can reveal operational activity and project timing.

Executive priority

Treat as a privacy and operational information exposure issue. Prioritize remediation for internet-facing Jira or environments containing sensitive project, client, or staffing data.

Technical view

Several Jira worklog REST resources before 7.13.7, and 8.0.0 before 8.3.2, lacked a required permission check. The CVE maps to CWE-863, incorrect authorization, allowing remote access to worklog time information beyond intended permissions.

Likely exposure

Organizations running affected Jira versions are exposed, especially where Jira is internet-facing or accessible to many users. The bundle does not clarify authentication requirements, deployment variants, or exact REST endpoints.

Exploitation context

The source bundle does not cite active exploitation, and CISA KEV status is false. Public references from Atlassian and Talos support the vulnerability details, but no exploitation-in-the-wild evidence is provided here.

Researcher notes

Evidence supports incorrect authorization in Jira worklog REST resources. The provided bundle lacks CVSS, endpoint details, authentication context, and exploit telemetry, so validation should focus on version exposure and vendor guidance.

Mitigation direction

  • Upgrade Jira to 7.13.7, 8.3.2, or later supported versions.
  • Check Atlassian advisory guidance for any version-specific remediation notes.
  • Restrict Jira access to trusted networks where practical.
  • Review permissions around worklog visibility and project access.

Validation and detection

  • Inventory Jira versions and identify systems before 7.13.7 or 8.3.2.
  • Confirm whether Jira is externally reachable or broadly accessible internally.
  • Review access logs for unusual worklog REST resource requests.
  • Verify upgraded instances no longer match affected version ranges.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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.

cwe · medium confidence lookup

CWE-863: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2019-8445 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
AtlassianJiraunspecified, 8.0.0, unspecifiedListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-863 · source CWE mapping

Incorrect Authorization

Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.