Microsoft Windows up to Server 2019 LUAFV Driver luafv.sys access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.2 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Microsoft Windows. Impacted is an unknown function in the library luafv.sys of the component LUAFV Driver. The manipulation leads to access control. This vulnerability is listed as CVE-2019-0796. The attack may be initiated remotely. There is no available exploit. It is suggested to install a patch to address this issue.
Details
A vulnerability, which was classified as problematic, has been found in Microsoft Windows (Operating System). This issue affects an unknown code in the library luafv.sys of the component LUAFV Driver. The manipulation with an unknown input leads to a access control vulnerability. Using CWE to declare the problem leads to CWE-264. Impacted is confidentiality, integrity, and availability.
The bug was discovered 04/09/2019. The weakness was presented 04/09/2019 as confirmed security update guide (Website). The advisory is shared at portal.msrc.microsoft.com. The public release was coordinated in cooperation with Microsoft. The identification of this vulnerability is CVE-2019-0796 since 11/26/2018. The attack may be initiated remotely. A simple authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1068 for this issue. The advisory points out:
An elevation of privilege vulnerability exists when Windows improperly handles calls to the LUAFV driver (luafv.sys). An attacker who successfully exploited this vulnerability could set the short name of a file with a long name to an arbitrary short name, overriding the file system with limited privileges.
It is declared as proof-of-concept. The commercial vulnerability scanner Qualys is able to test this issue with plugin 91522 (Microsoft Windows Security Update for April 2019).
Applying a patch is able to eliminate this problem. A possible mitigation has been published immediately after the disclosure of the vulnerability.
See VDB-133196, VDB-133195, VDB-133194 and VDB-133192 for similar entries. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
- 7 SP1
- 8.1
- 10
- 10 1607
- 10 1703
- 10 1709
- 10 1803
- 10 1809
- RT 8.1
- Server 1709
- Server 1803
- Server 2008 R2 SP1
- Server 2008 SP2
- Server 2012
- Server 2012 R2
- Server 2016
- Server 2019
License
Website
- Vendor: https://www.microsoft.com/
- Product: https://www.microsoft.com/en-us/windows
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.2
VulDB Base Score: 4.3
VulDB Temp Score: 3.9
VulDB Vector: 🔍
VulDB Reliability: 🔍
Vendor Base Score (Microsoft): 6.3
Vendor Vector (Microsoft): 🔍
NVD Base Score: 5.5
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Access controlCWE: CWE-264
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Qualys ID: 🔍
Qualys Name: 🔍
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Timeline
11/26/2018 🔍04/09/2019 🔍
04/09/2019 🔍
04/09/2019 🔍
04/10/2019 🔍
10/19/2025 🔍
Sources
Vendor: microsoft.comProduct: microsoft.com
Advisory: 152535
Status: Confirmed
Coordinated: 🔍
CVE: CVE-2019-0796 (🔍)
GCVE (CVE): GCVE-0-2019-0796
GCVE (VulDB): GCVE-100-133193
scip Labs: https://www.scip.ch/en/?labs.20161215
See also: 🔍
Entry
Created: 04/10/2019 07:12Updated: 10/19/2025 21:11
Changes: 04/10/2019 07:12 (71), 05/27/2020 21:15 (2), 08/28/2023 06:43 (6), 07/11/2024 23:28 (18), 10/19/2025 21:11 (7)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.