GHSA-6Q65-J4JW-9CG8
Vulnerability from github – Published: 2025-06-19 14:40 – Updated: 2025-06-19 14:40Description
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
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 4.3.7"
},
"package": {
"ecosystem": "NuGet",
"name": "DotVVM"
},
"ranges": [
{
"events": [
{
"introduced": "4.3.0-preview01-final"
},
{
"fixed": "4.3.8"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "NuGet",
"name": "DotVVM"
},
"ranges": [
{
"events": [
{
"introduced": "5.0.0-preview01-final"
},
{
"fixed": "5.0.0-preview03-final"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "NuGet",
"name": "DotVVM"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "4.2.10"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": true,
"github_reviewed_at": "2025-06-19T14:40:30Z",
"nvd_published_at": null,
"severity": "HIGH"
},
"details": "### Description\n\nThere 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).\n\n### Patches\n\nThe bug is patched in versions **4.2.10**, **4.3.8** and **5.0.0-preview03-final** (and newer).\n\nApart 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).\n\n### Workarounds\n\nIf 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:\n\n```\n config.Debug = false; // TODO: workaround for GHSA-6q65-j4jw-9cg8, remove after updating DotVVM\n```",
"id": "GHSA-6q65-j4jw-9cg8",
"modified": "2025-06-19T14:40:30Z",
"published": "2025-06-19T14:40:30Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/riganti/dotvvm/security/advisories/GHSA-6q65-j4jw-9cg8"
},
{
"type": "WEB",
"url": "https://github.com/riganti/dotvvm/commit/68db0110beeda4e8e4be1b7c4e480ef876895bb5"
},
{
"type": "PACKAGE",
"url": "https://github.com/riganti/dotvvm"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
],
"summary": "DotVVM allows path traversal when deployed in Debug mode"
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.