Automation For JiraApplication · Atlassian
CVE-2020-14193
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAffected 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceServer-side template injection vulnerability in Automation for Jira allows remote attackers to read and render files as Mustache templates by exploiting mustache partials in Jira smart values. Attackers can access files in WEB-INF/classes and <jira-installation>/jira/bin directories via crafted smart value input.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Automation For JiraApplication
< 7.1.15CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Automation for Jira versionNavigate to Jira Administration > Apps > Manage apps or check the /rest/plugins/1.0/ endpoint to find the installed version of 'Automation for Jira' appAffected if The version listed is less than 7.1.15 (e.g., 7.1.14, 7.0.x, 6.x)
-
Verify Automation for Jira is enabledCheck in Jira Administration > Apps > Manage apps that the Automation for Jira app shows as 'Enabled' and not 'Disabled' or 'Uninstalled'Affected if The app is enabled and running with a vulnerable version
-
Confirm user access to automation rulesCheck if any users or groups have permissions to create or edit automation rules in Jira (Administration > Issues > Automation > Rule permissions or Project settings > Automation)Affected if Non-admin users can create or edit automation rules, allowing them to inject malicious smart value input
-
Review existing automation rules for smart value usageNavigate to Administration > Automation or project-level automation rules and inspect rules that use smart values in conditions, actions, or triggersAffected if Rules with smart value fields exist, as these are the vectors for the mustache template injection
You are affected if Automation for Jira is installed and enabled with a version lower than 7.1.15, and users have permission to create or edit automation rules containing smart values.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data7.1.15
Upgrade Automation for Jira to version 7.1.15 or later to remediate the template injection vulnerability.
Fix this in Automation For Jira
Scoped from the published advisory
- Consultation3.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-14193 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-14193 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data