Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

NuGet package

dotvvm

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 7.5NuGetPublished

    DotVVM allows path traversal when deployed in Debug mode

    GHSA-6q65-j4jw-9cg8

    Affected
    • NuGet dotvvm >= 4.3.0-preview01-final, <= 4.3.7; >= 5.0.0-preview01-final, < 5.0.0-preview03-final; < 4.2.10
    Fixed in
    4.2.105.0.0-preview03-final4.3.8· Vendor fix available
    Issue
    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:

    Recommended action: Upgrade to 5.0.0-preview03-final (pre-release), 4.3.8 or 4.2.10 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →