Security readout for executives and security teams
Plain-English summary
This vulnerability affects Atlassian's gajira-comment GitHub Action before 2.0.2. A malicious issue comment could cause arbitrary code to run on a GitHub Actions runner. For leaders, the concern is unauthorized code execution inside CI, where build secrets or deployment permissions may be present.
Executive priority
Treat as high priority if the action was used in repositories with secrets, deployment credentials, or privileged CI permissions. If not used, no direct exposure is indicated by the provided sources.
Technical view
CVE-2020-14189 is a remote code execution issue in the execute function of atlassian/gajira-comment before 2.0.2. The trigger is a specially crafted GitHub issue comment, with execution occurring in the context of the GitHub runner. The source bundle does not provide CVSS, CWE, exploit detail, or broader product impact.
Likely exposure
Exposure is likely limited to repositories using the Atlassian gajira-comment GitHub Action before version 2.0.2, especially workflows connected to issue comments. The bundle does not identify affected CPEs or exact vulnerable version ranges beyond before 2.0.2.
Exploitation context
The bundle does not show CISA KEV listing or evidence of active exploitation. It does state that remote attackers can execute arbitrary code through a specially crafted GitHub issue comment. No exploit maturity, public exploit availability, or attack prevalence is provided.
Researcher notes
The record is sparse: no CVSS, CWE, CPEs, exploit status, or detailed remediation notes are included. Analysis should stay anchored to the GitHub advisory and CVE record, then verify real exposure through repository workflow configuration.
Mitigation direction
- Upgrade atlassian/gajira-comment to version 2.0.2 or later where used.
- Inventory GitHub Actions workflows for gajira-comment references.
- Review vendor advisory for any additional Atlassian guidance.
- Assess exposed CI secrets if vulnerable workflows ran on untrusted comments.
- Restrict risky comment-triggered workflows where operationally feasible.
Validation and detection
- Search workflow files for atlassian/gajira-comment usage.
- Confirm referenced action versions are 2.0.2 or later.
- Identify workflows triggered by issue comments or related events.
- Review recent workflow runs for unexpected executions from issue comments.
- Check whether runner jobs had access to sensitive secrets or deployments.
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.
Execution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2020-14189 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://github.com/atlassian/gajira-comment/security/advisories/GHSA-hj6w-pm28-h8hfCVE 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.