# CVE-2020-14189: Code injection in gajira-comment

> Remote attackers can execute arbitrary code on GitHub runners by crafting malicious issue comments in the Atlassian gajira-comment action.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Nov 2020
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-hj6w-pm28-h8hf

## What is CVE-2020-14189?

CVE-2020-14189 is a critical code injection vulnerability in Atlassian gajira-comment, published on 9 Nov 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2020-14189?

It affects 1 product.


Products: Atlassian Jira Comment.

## How do I fix CVE-2020-14189?

No fix has been published for CVE-2020-14189 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-14189 being exploited?

There is no known exploitation of CVE-2020-14189 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-14189 and fix it if it is affected.

What it is: CVE-2020-14189 is a critical code injection vulnerability in Atlassian gajira-comment, published on 9 Nov 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-14189 in the wild and no public exploit code.

Affected product: Atlassian gajira-comment. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-14189/ (Markdown: https://insights.sbomify.com/CVE-2020-14189/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-14189
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-14189
- OSV: https://osv.dev/vulnerability/CVE-2020-14189

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-14189/
Summaries are generated and may contain mistakes; the official description above is the record.