Skip to content
Fencer Intel
high 7.5

GHSA-6q65-j4jw-9cg8 json

DotVVM allows path traversal when deployed in Debug mode

published last yr. modified last yr.

cvss
7.5
version 3.1, GitHub
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

### 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 ```

Patch / fix

  • nuget DotVVM 4.2.10, 4.3.8, 5.0.0-preview03-final

Is GHSA-6q65-j4jw-9cg8 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CVSS scores

assigned by version score vector
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
nuget DotVVM
>=4.3.0-preview01-final, <4.3.8
>=5.0.0-preview01-final, <5.0.0-preview03-final
<4.2.10
4.3.8
5.0.0-preview03-final
4.2.10

Classification

Weakness
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.