GHSA-8mfq-f5wj-vw5m: Nautobot vulnerable to remote code execution via Jinja2 template rendering
Impact_What kind of vulnerability is it? Who is impacted?_All users of Nautobot versions earlier than 1.5.7 are impacted.In Nautobot 1.5.7 we have enabled sandboxed environments for the Jinja2 template engine used internally for template rendering for the following objects:`extras.ComputedField``extras.CustomLink``extras.ExportTemplate``extras.Secret``extras.Webhook`While we are not aware of any active exploits, we have made this change as a preventative measure to protect against any potential remote code execution attacks utilizing maliciously crafted template code.This change forces the Jinja2 template engine to use a [`SandboxedEnvironment`](https://jinja.palletsprojects.com/en/3.0.x/sandbox/#sandbox) on all new installations of Nautobot.This addresses any potential unsafe code execution everywhere the helper function `nautobot.utilities.utils.render_jinja2` is called. Additionally, our documentation that was previously suggesting the direct use of `jinja2.Template` has been revised to utilize `render_jinja2`.Patches_Has the problem been patched? What versions should users upgrade to?_Yes. Users should upgrade to Nautobot 1.5.7 or newer.Workarounds_Is there a way for users to fix or remediate the vulnerability without upgrading?_Enabling Sandboxed EnvironmentsFor users that are unable to upgrade to the latest release of Nautobot, you may add the following setting to your `nautobot_config.py` to apply the sandbox environment enforcement:After applying this change, you must restart all Nautobot services, including any Celery worker processes.**Note:** *Nautobot specifies two template engines by default, the first being “django” for the Django built-in template engine, and the second being “jinja” for the Jinja2 template engine. This recommended setting will update the second item in the list of template engines, which is the Jinja2 engine.*Restricting Jinja2 using Access ControlsFor users that are unable to immediately update their configuration such as if a Nautobot service restart is too disruptive to operations, access to provide custom Jinja2 template values may be mitigated using permissions to restrict “change” (write) actions to the affected object types listed in the first section.**Note:** *This solution is intended to be stopgap until you can successfully update your `nautobot_config.py` or upgrade your Nautobot instance to apply the sandboxed environment enforcement.*Updating Existing App or Job CodeFor Nautobot App (formerly plugin) authors or Job authors, additionally we recommend that if you have any custom code that may for example be using `jinaj2.Template` that you no longer use that. Instead, please always use our `nautobot.utilities.utils.render_jinja2` function which will make sure that the centrally-provided Jinja2 template engine with sandboxing enforced is being utilized.Anywhere you’ve been using this pattern:We recommend that you replace it with this pattern:References_Are there any links users can visit to find out more?_Please see the Nautobot 1.5.7 release notes.https://docs.nautobot.com/projects/core/en/stable/release-notes/version-1.5/#v157-2023-01-04
CVSS v4.0: 7.7
CVSS v3.1: 7.5