Nautobot is a Network Source of Truth and Network Automation Platform. All users of Nautobot versions earlier than 1.5.7 are impacted by a remote code execution vulnerability. Nautobot did not properly sandbox Jinja2 template rendering. In Nautobot 1.5.7 has 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 no active exploits of this vulnerability are known this change has been made 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` 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, the documentation that had previously suggesting the direct use of `jinja2.Template` has been revised to suggest `render_jinja2`. Users are advised to upgrade to Nautobot 1.5.7 or newer. For 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: `TEMPLATES[1]["OPTIONS"]["environment"] = "jinja2.sandbox.SandboxedEnvironment"` 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.* For 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.*

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - Nautobot is a Network Source of Truth and Network Automation Platform. All users of Nautobot versions
    earlier than 1.5.7 are impacted by a remote code execution vulnerability. Nautobot did not properly
    sandbox Jinja2 template rendering. In Nautobot 1.5.7 has 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 no active exploits
    of this vulnerability are known this change has been made 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` 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, the documentation that had previously
    suggesting the direct use of `jinja2.Template` has been revised to suggest `render_jinja2`. Users are
    advised to upgrade to Nautobot 1.5.7 or newer. For 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: `TEMPLATES[1]["OPTIONS"]["environment"] = "jinja2.sandbox.SandboxedEnvironment"`
    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.* For
    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.*
    (CVE-2023-25657)

ID	Name	Product	Family	Severity
412757	SCA: security update for nautobot (GHSA-8mfq-f5wj-vw5m)	Tenable Cloud Security	SCA Checks	high
412757	SCA: security update for nautobot (GHSA-8mfq-f5wj-vw5m)	Tenable Self-Hosted Container Security	SCA Checks	high

Detections

Analytics

CVE-2023-25657

high

Tenable Plugins

high

high