# CVE-2020-14193: Code injection in Automation for Jira

> Remote attackers can read and render files as mustache templates via template injection in Jira smart values, exposing sensitive data.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Nov 2020
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-q38p-89cx-mcrc

## What is CVE-2020-14193?

CVE-2020-14193 is a medium-severity code injection vulnerability in Atlassian Automation for Jira, published on 30 Nov 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Affected versions of Automation for Jira - Server allowed remote attackers to read and render files as mustache templates in files inside the WEB-INF/classes & <jira-installation>/jira/bin directories via a template injection vulnerability in Jira smart values using mustache partials. The affected versions are those before version 7.1.15.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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

It affects 1 product.


Products: Atlassian Automation for Jira.

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

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

## Is CVE-2020-14193 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-14193 is a medium-severity code injection vulnerability in Atlassian Automation for Jira, published on 30 Nov 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-14193 in the wild and no public exploit code.

Affected product: Atlassian Automation for Jira. 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-14193/ (Markdown: https://insights.sbomify.com/CVE-2020-14193/index.md)
```

## Sources

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

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