CVE-2020-14189
First published: Mon Nov 09 2020(Updated: )
The execute function in in the Atlassian gajira-comment GitHub Action before version 2.0.2 allows remote attackers to execute arbitrary code in the context of a GitHub runner by creating a specially crafted GitHub issue comment.
Credit: security@atlassian.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Atlassian Jira Comment | <2.0.2 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Frequently Asked Questions
What is the severity of CVE-2020-14189?
CVE-2020-14189 is classified as a critical vulnerability due to its ability to allow arbitrary code execution.
How do I fix CVE-2020-14189?
To fix CVE-2020-14189, update the Atlassian gajira-comment GitHub Action to version 2.0.2 or later.
What type of attacks can exploit CVE-2020-14189?
CVE-2020-14189 can be exploited by remote attackers through crafted GitHub issue comments.
Who is affected by CVE-2020-14189?
Users of the Atlassian gajira-comment GitHub Action prior to version 2.0.2 are affected by CVE-2020-14189.
What is the impact of CVE-2020-14189?
The impact of CVE-2020-14189 is that it may allow attackers to execute arbitrary code in the context of a GitHub runner.
- collector/nvd-index
- agent/type
- agent/softwarecombine
- agent/author
- agent/severity
- agent/references
- agent/tags
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/first-publish-date
- agent/event
- agent/source
- vendor/atlassian
- canonical/atlassian jira comment