Atlassian Confluence Server and Data Center Server-Side Template Injection
CVE-2019-3396 is a critical-severity improper limitation of a pathname to a restricted directory vulnerability in Confluence Server from Atlassian, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 6.6.12, 6.12.3, 6.13.3 as the first without the flaw, so updating Confluence Server to one of those releases or later removes the exposure. CISA added it to the Known Exploited Vulnerabilities catalogue on November 3, 2021, which means attacks have been observed in the wild, including in ransomware campaigns.
Attackers are already exploiting this vulnerability, according to CISA.
What to do
- Update Confluence Server to 6.6.12 or 6.12.3 or 6.13.3 or 6.14.2, whichever matches your release line, or a later version.
- CISA's required action: Apply updates per vendor instructions.
- Read the advisory on jira.atlassian.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Atlassian | Confluence Server | before 6.6.12; 6.7.0; before 6.12.3; next of 6.13.0; before 6.13.3; next of 6.14.0; before 6.14.2 | 6.6.12, 6.12.3, 6.13.3, 6.14.2 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 9.8 | Critical | NVD |
| CVSS 3.1 | 9.8 | Critical | CISA (ADP) |
| CVSS 2.0 | 10.0 | High | NVD |
Official description
The Widget Connector macro in Atlassian Confluence Server before version 6.6.12 (the fixed version for 6.6.x), from version 6.7.0 before 6.12.3 (the fixed version for 6.12.x), from version 6.13.0 before 6.13.3 (the fixed version for 6.13.x), and from version 6.14.0 before 6.14.2 (the fixed version for 6.14.x), allows remote attackers to achieve path traversal and remote code execution on a Confluence Server or Data Center instance via server-side template injection.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Limitation of a Pathname to a Restricted Directory
The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
How developers prevent this class of flaw
- For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
- Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth.
More Improper Limitation of a Pathname to a Restricted Directory vulnerabilities (CWE-22)
Timeline
- CVE record published.
- Added to CISA's Known Exploited Vulnerabilities catalogue.
- Deadline for US federal agencies to remediate, set by CISA.
- CISA published its SSVC assessment (exploitation: active, automatable: yes, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Advisories
- jira.atlassian.com/browse/CONFSERVER-57974Issue Tracking
Third-party and government advisories
- cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2019-3396US Government Resource
Technical write-ups (may include proof of concept)
- packetstormsecurity.com/files/152568/Atlassian-Confluence-Widget-Connector-Macro-Velocity-Template-Injection…Exploit, Third Party Advisory, VDB Entry
- packetstormsecurity.com/files/161065/Atlassian-Confluence-6.12.1-Template-Injection.htmlExploit, Third Party Advisory, VDB Entry
- rapid7.com/db/modules/exploit/multi/http/confluence_widget_connectorExploit, Third Party Advisory, VDB Entry
- exploit-db.com/exploits/46731/Exploit, Third Party Advisory, VDB Entry
Other vulnerabilities in Confluence Server
- 9.3 Critical severity
- 7.5 High severity
- 8.2 High severity
- 8.7 High severity
- 8.8 High severity
- 8.8 High severity
Recent Improper Limitation of a Pathname to a Restricted Directory vulnerabilities
- 6.5 Medium severity
- 7.8 High severity
WinRAR Absolute Path Traversal Exploited
- 9.1 Critical severity
MikroTik Router OS Directory Traversal Exploited
- 7.5 High severity
- 8.8 High severity
- 6.6 Medium severity
Spotted an error? Tell us.