vitejs Vite up to 5.4.5 File Content information disclosure

Summaryinfo

A vulnerability marked as problematic has been reported in vitejs Vite up to 3.2.10/4.5.4/5.2.13/5.3.5/5.4.5. Impacted is an unknown function of the component File Content Handler. The manipulation leads to information disclosure. This vulnerability is traded as CVE-2024-45811. Access to the local network is required for this attack to succeed. There is no exploit available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability was found in vitejs Vite up to 3.2.10/4.5.4/5.2.13/5.3.5/5.4.5 and classified as problematic. This issue affects an unknown code of the component File Content Handler. The manipulation with an unknown input leads to a information disclosure vulnerability. Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality. The summary by CVE is:

Vite a frontend build tooling framework for javascript. In affected versions the contents of arbitrary files can be returned to the browser. `@fs` denies access to files outside of Vite serving allow list. Adding `?import&raw` to the URL bypasses this limitation and returns the file content if it exists. This issue has been patched in versions 5.4.6, 5.3.6, 5.2.14, 4.5.5, and 3.2.11. Users are advised to upgrade. There are no known workarounds for this vulnerability.

It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2024-45811 since 09/09/2024. The exploitation is known to be difficult. The attack needs to be initiated within the local network. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.

Upgrading to version 3.2.11, 4.5.5, 5.2.14, 5.3.6 or 5.4.6 eliminates this vulnerability. Applying the patch 6820bb3b9a54334f3268fc5ee1e967d2e1c0db34 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.

Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Vendor

• vitejs

Name

• Vite

Version

• 3.2.0
• 3.2.1
• 3.2.2
• 3.2.3
• 3.2.4
• 3.2.5
• 3.2.6
• 3.2.7
• 3.2.8
• 3.2.9
• 3.2.10
• 4.5.0
• 4.5.1
• 4.5.2
• 4.5.3
• 4.5.4
• 5.2.0
• 5.2.1
• 5.2.2
• 5.2.3
• 5.2.4
• 5.2.5
• 5.2.6
• 5.2.7
• 5.2.8
• 5.2.9
• 5.2.10
• 5.2.11
• 5.2.12
• 5.2.13
• 5.3.0
• 5.3.1
• 5.3.2
• 5.3.3
• 5.3.4
• 5.3.5
• 5.4.0
• 5.4.1
• 5.4.2
• 5.4.3
• 5.4.4
• 5.4.5

License

• open-source

Website

• Product: https://github.com/vitejs/vite/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion