CVE-2020-14188
First published: Wed Oct 28 2020(Updated: )
The preprocessArgs function in the Atlassian gajira-create GitHub Action before version 2.0.1 allows remote attackers to execute arbitrary code in the context of a GitHub runner by creating a specially crafted GitHub issue.
Credit: security@atlassian.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Atlassian Jira | <2.0.1 |
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-14188?
CVE-2020-14188 has been classified as a high severity vulnerability due to the potential for remote code execution.
How do I fix CVE-2020-14188?
To fix CVE-2020-14188, upgrade the Atlassian Jira Create GitHub Action to version 2.0.1 or later.
What could happen if CVE-2020-14188 is exploited?
If exploited, CVE-2020-14188 allows remote attackers to execute arbitrary code in the system running the GitHub Actions runner.
What versions are affected by CVE-2020-14188?
CVE-2020-14188 affects all versions of the Atlassian Jira Create GitHub Action prior to version 2.0.1.
Is there a proof of concept for CVE-2020-14188?
While a specific proof of concept has not been publicly disclosed, the vulnerability's description suggests that creating a specially crafted GitHub issue can exploit it.
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/references
- agent/last-modified-date
- agent/author
- agent/severity
- agent/description
- agent/first-publish-date
- agent/event
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/atlassian
- canonical/atlassian jira