Summaryinfo

A vulnerability marked as critical has been reported in nautobot 2.0.0/2.0.1/2.0.2. This issue affects some unknown processing of the component REST API. This manipulation causes private personal information. This vulnerability is tracked as CVE-2023-46128. The attack is possible to be carried out remotely. Moreover, an exploit is present. It is suggested to upgrade the affected component. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Detailsinfo

A vulnerability has been found in nautobot 2.0.0/2.0.1/2.0.2 and classified as problematic. Affected by this vulnerability is an unknown code of the component REST API. The manipulation with an unknown input leads to a private personal information vulnerability. The CWE definition for the vulnerability is CWE-359. The product does not properly prevent a person's private, personal information from being accessed by actors who either (1) are not explicitly authorized to access the information or (2) do not have the implicit consent of the person about whom the information is collected. As an impact it is known to affect confidentiality. The summary by CVE is:

Nautobot is a Network Automation Platform built as a web application atop the Django Python framework with a PostgreSQL or MySQL database. In Nautobot 2.0.x, certain REST API endpoints, in combination with the `?depth=` query parameter, can expose hashed user passwords as stored in the database to any authenticated user with access to these endpoints. The passwords are not exposed in plaintext. This vulnerability has been patched in version 2.0.3.

The weakness was disclosed 10/24/2023 as GHSA-r2hw-74xv-4gqp. It is possible to read the advisory at github.com. This vulnerability is known as CVE-2023-46128 since 10/16/2023. Technical details are unknown but a public exploit is available. The attack technique deployed by this issue is T1589 according to MITRE ATT&CK.

It is possible to download the exploit at github.com. It is declared as proof-of-concept.

Upgrading to version 2.0.3 eliminates this vulnerability. Applying the patch 1ce8e5c658a075c29554d517cd453675e5d40d71 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Name

• nautobot

Version

• 2.0.0
• 2.0.1
• 2.0.2

License

• open-source

Website

• Product: https://github.com/nautobot/nautobot/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Discussion