DotVVM: Missing authorization in AuthorizeActionFilter
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| riganti | dotvvm | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Riganti | Dotvvm |
|
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.624% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Riganti
Riganti dotvvm |
|
| Vendors & Products |
Riganti
Riganti dotvvm |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | DotVVM is an open source MVVM framework for web applications. Prior to 4.2.11, 4.3.15, and 5.0.0-preview09-final, AuthorizeActionFilter performs no authorization because its explicit ICommandActionFilter.OnCommandExecutingAsync, IViewModelActionFilter.OnViewModelCreatedAsync, and IPresenterActionFilter.OnPresenterExecutingAsync implementations return completed tasks instead of invoking the corresponding checks. Applications relying on this filter can therefore expose protected commands, view models, or presenters to unauthorized requests without any special bypass technique. AuthorizeAttribute correctly implements the same interfaces and can be used as a workaround. This issue is fixed in versions 4.2.11, 4.3.15, and 5.0.0-preview09-final. | |
| Title | DotVVM: Missing authorization in AuthorizeActionFilter | |
| Weaknesses | CWE-862 | |
| References |
|
|
| Metrics |
cvssV4_0
|