Skip to content

XSS potential in rendered Markdown fields (comments, description, notes, etc.)

High
glennmatthews published GHSA-v4xv-795h-rv4h Jan 22, 2024

Package

pip nautobot (pip)

Affected versions

<1.6.10,<2.1.2

Patched versions

1.6.10,2.1.2

Description

Impact

What kind of vulnerability is it? Who is impacted?

All users of Nautobot versions earlier than 1.6.10 or 2.1.2 are potentially impacted.

Due to inadequate input sanitization, any user-editable fields that support Markdown rendering, including:

  • Circuit.comments
  • Cluster.comments
  • CustomField.description
  • Device.comments
  • DeviceRedundancyGroup.comments
  • DeviceType.comments
  • Job.description
  • JobLogEntry.message
  • Location.comments
  • Note.note
  • PowerFeed.comments
  • Provider.noc_contact
  • Provider.admin_contact
  • Provider.comments
  • ProviderNetwork.comments
  • Rack.comments
  • Tenant.comments
  • VirtualMachine.comments
  • Contents of any custom fields of type markdown
  • Job class description attributes
  • The SUPPORT_MESSAGE system configuration setting

are potentially susceptible to cross-site scripting (XSS) attacks via maliciously crafted data.

Patches

Has the problem been patched? What versions should users upgrade to?

Fixed in Nautobot versions 1.6.10 and 2.1.2.

Workarounds

Is there a way for users to fix or remediate the vulnerability without upgrading?

References

Are there any links users can visit to find out more?

#5133
#5134

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
High
Availability
Low

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:L/I:H/A:L

CVE ID

CVE-2024-23345

Weaknesses

Credits