Skip to content

DotVVM allows path traversal when deployed in Debug mode

High severity GitHub Reviewed Published Jun 19, 2025 in riganti/dotvvm • Updated Jun 19, 2025

Package

nuget DotVVM (NuGet)

Affected versions

>= 4.3.0-preview01-final, <= 4.3.7
>= 5.0.0-preview01-final, < 5.0.0-preview03-final
< 4.2.10

Patched versions

4.3.8
5.0.0-preview03-final
4.2.10

Description

Description

There is a path traversal vulnerability in any DotVVM application started in Debug mode, if at least one resource with the FileResourceLocation has been added. The vulnerability allows an attacker to read arbitrary files from the filesystem accessible by the web application (i.e. appsettings.json or other files containing secrets).

Patches

The bug is patched in versions 4.2.10, 4.3.8 and 5.0.0-preview03-final (and newer).

Apart from updating DotVVM, it is also recommend invalidating any secrets which could have been leaked by an application deployed in Debug mode (such as database passwords).

Workarounds

If you cannot update to a patched version, avoid running a publicly accessible DotVVM application in Debug mode (Development environment in Asp.Net Core). It is recommend adding the following statement to the DotvvmStartup class:

    config.Debug = false; // TODO: workaround for GHSA-6q65-j4jw-9cg8, remove after updating DotVVM

References

@exyi exyi published to riganti/dotvvm Jun 19, 2025
Published to the GitHub Advisory Database Jun 19, 2025
Reviewed Jun 19, 2025
Last updated Jun 19, 2025

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
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS score

Weaknesses

CVE ID

No known CVE

GHSA ID

GHSA-6q65-j4jw-9cg8

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.