External Control of File Name or Path (CWE-73)
VNote, a note-taking platform, contains a code execution vulnerability in versions prior to 3.18.1. This vulnerability allows an attacker to execute arbitrary programs on the victim's system by using a crafted URI with the file:/// scheme as a link within a note. For example, an attacker could embed references to local executable files such as file:///C:/WINDOWS/system32/cmd.exe or file:///C:/WINDOWS/system32/calc.exe in a note. This vulnerability can be exploited by creating and sharing specially crafted notes.
The impact of this vulnerability is severe. An attacker can execute arbitrary programs on the victim's system, potentially leading to full system compromise. This could result in unauthorized access, data theft, system manipulation, or further malware installation. The vulnerability has high impacts on confidentiality, integrity, and availability of the affected system. The CVSS v3.1 base score is 8.8, indicating a high severity level.
There is no evidence that a public proof-of-concept exists. There is no evidence of proof of exploitation at the moment.
A patch is available. The vulnerability has been fixed in VNote version 3.18.1.
1. Upgrade VNote to version 3.18.1 or later immediately. 2. If immediate upgrading is not possible, avoid opening notes from untrusted sources. 3. Implement strict input validation and sanitization for all user-supplied content, especially URLs and file paths. 4. Consider disabling the ability to use file:/// URIs in notes if this feature is not critical for operations. 5. Educate users about the risks of opening notes from unknown sources. 6. Monitor systems for any suspicious activities or unexpected program executions.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD published the first details for CVE-2024-39904
A CVSS base score of 8.8 has been assigned.
Feedly found the first article mentioning CVE-2024-39904. See article
Feedly estimated the CVSS score as HIGH
This CVE started to trend in security discussions
EPSS Score was set to: 0.04% (Percentile: 9.2%)
This CVE stopped trending in security discussions